ROOL Forum: Recent posts

Sat, 13 Jun 2026 17:46:29 +0000

Thanks Charles,
Private Access Token:I couldn’t find it in my settings
I’m not yet the best at exchanging keys…still learning.

I would have liked to upload the versions of MkDrawf (Gareth MacCaughan) as you did and it seems that you also made corrections.
I must take inspiration from your work to present things correctly.

Sat, 13 Jun 2026 13:35:25 +0000

Just to update people.

I’m still struggling with having David’s app work for me. Probably down to my dimwittery, etc. However I’ve also been re-looking at my Compo-based approach as it seems more like the ‘way I think’ (sic?). I should be able to automate that to run through a series of jpegs. At present it outputs the clean results as different a different image format, but I’ll change that to saving out single-page jpegs.

If I can get that to work it will employ the ‘expand blue as grey’ trick that provides get adapting fuller contrast for the grescale output. Composcript will ‘loop’ so if I can get that working it should then be OK chugging through pages. The resulty being a new set of page jpegs that have been debrowed and optimised in brightness.contrast.

Overall, that means I’d have a multi-stage process.

1) Export the pages from a PDF as page jpegs, numbered in order in a directory

2) Have the Compo-based method generate ‘detoxed’ those jpegs, again one per page, by looping though the input jpegs. (But perhaps not decolouring the first image as that’s often a decent colour cover because chinered paper doesn’t brown like pulp (content) paper.

3) Then convert each jpeg page into a PDF

4) Then use a method for putting these jpeg pages into one PDF.

Seems strange that we can’t simply “add another jpeg” as another page at the end of a PDF. But can add one single-page PDF, one after another. Or am I misunderstanding that as well?! It would be simpler in filer-terms (and my brain!) if each page could be tacked onto the end of the ones already in an output PDF.

Sat, 13 Jun 2026 13:14:37 +0000

Pushing to a HTTPS GitHub address is possible for git – you just need to supply a Private Access Token (PAT) as the password – you cannot use your standard GitHub password. In my experience it’s a lot easier using the HTTPS location because you don’t have to mess around with ssh keys or reusing an SSH key for another service (which means that compromising the SSH key doesn’t expose the HTTP services that you use as well as everything else).

Sat, 13 Jun 2026 13:00:17 +0000

Hi All,

StrongMen 1.28f1 is now available for download my website

Due to the long delay since the last release I’ve decided to move for a stable version of 1.28. As no bugs were reported after a beta release to the StrongED mailing list, the status of v1.28 has now been changed to stable.

Changes

There’s only one change, from the previous last public test release (1.28a2), which is support for colours. A submenu can have a coloured title and/or coloured items.

Individual items can have their own colour, overriding any submenu colour. Each colour is specified as a 6-digit hex number allowing any colour in the 32-bit colour space to be used.

StrongMen mode

Included is an updated version of the StrongMen mode for StrongED that has gained an add-on for easy insertion of colours into the StrongMenu file.

As always, all feedback is welcome.

Sat, 13 Jun 2026 08:31:40 +0000

Sorry Steve and Sprow, I missed your answers, I’ll look, thanks.

Sat, 13 Jun 2026 08:29:54 +0000

David,
thanks for ssh-keygen, I was using the !SSH version.
I updated my Github site settings and add the keys to choices.WWW

Steve,
For my test:
• I clone a test project from Github
• Git client is running ,I click on /git in the directory.
• I get the log windows
• git status ok.
• Modification in readme, git satus saw it.
• git add
• git commit -m “modification”
• I get a new branch in log window: main
• git remote -v
origin https://github.com/Jean-MichelB/Sort (fetch)
origin https://github.com/Jean-MichelB/Sort (push)

• git push origin main
  Username for ‘https://github.com/Jean-MichelB/Sort’: username
  Username for ‘https://github.com/Jean-MichelB/Sort’: password

result: git2 :unexpected EOF :-(
Access is via the https address…
I follow the instructions in the git 1.0.0 “User guide” PDF document with help from the StrongEd manual Gitclient.

I found a good book on Git (also available in French): Pro Git.
This allowed me to better understand the interest of Git and its use which can prove beneficial even locally, a good tool.

Sat, 13 Jun 2026 08:01:38 +0000

…or just use SSH and avoid the faff with access tokens… :-)

Sat, 13 Jun 2026 07:24:45 +0000

SSH-KeyGen is included in the OS5.31 HardDisc4 image *ssh-keygen

The Git client expects the private half of the key in PEM format, so you want

*ssh-keygen -m pem

gleaned from RISC OS tips in the Git client help.

That said, for GitHub, don’t be lured onto the rocks entering a username and password. Password authentication was removed in August 2021 so instead, when pushing stuff from Windows at least, I:

• Log in to their website using the username and password
• Do any 2FA stuff
• Set up a personal access token with read/write access to the repository in question
• Take a note of the access token (a string of about 20 letters and numbers)
• Push your changes from Git
• When prompted for a username and password, the username is the one you logged into the website with, but the password is the access token string generated

Fri, 12 Jun 2026 19:06:51 +0000

Obvious question: what repository address have you given the Git client? The SSH one? Or the other one starting with https:// …?

Again, I’m fairly sure that you can’t push to the HTTPS address.

Fri, 12 Jun 2026 18:54:05 +0000

I’m sure I used ssh-keygen on RISC OS (can’t remember where I got that from, though!).

SSH-KeyGen is included in the OS5.31 HardDisc4 image.

*which ssh-keygen
File: SCSI::SSD120.$.!BOOT.Resources.!Internet.bin.ssh-keygen
*

*ssh-keygen
Generating public/private rsa key of 2048 bits
Writing private key to @.x2c567902
Writing public key to @.x2c567902/pub
*

This writes the keys to the CSD.

Fri, 12 Jun 2026 18:52:32 +0000

I must be doing something wrong…
I tried with a key generated differently, but ko…
1) location of the generated key: choices…WWW or SSH or choices.git

2)I copy and paste the public key into the add authentications keys location (my GitHub settings) naming it.

3)I pass the command git push, => name + pwd and I always get: git2:unexpected EOF :-(

Thanks.