Module "Line Editor" Download

I found today Line Editor 2.76d on my RISC OS. Not sure what application is loading it.
I found then the Github site
Line Editor sources

I don’t know if it is forbidden to upload on GitHub / GitLab compiled programs but I am pretty pissed off by that.
So no download of the module there. Only the source code.

I saw a discussion about “Line editor” on another post in bounties “Adopt Zap” but there was no link mentioned for a download too.
Adopt Zap

I wonder if it might be usefull to have all modules listed in Packman for easy updating.

I’m confused – I don’t see why the urological discussion is necessary on a forum about an operating system. I have no desire to know that your “piss” is “off”, but perhaps you should speak to a doctor.

All joking aside – the latest release is 2.77, and the module builds from the BASIC code. You double-click the “Release” obey file, or the BASIC source code, and it produces a module. I’m pretty sure it says this on the Github page.

Binary releases expire off of Github after 90 days, sadly I have no control over this: https://docs.github.com/en/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization

I didn’t know there was an “adopt Zap” bounty – I don’t really want to adopt the whole thing as I don’t have time to work on it, but it seems I’ve volunteered myself for LineEditor…

I don’t know how to build Packman packages, so that’s why they don’t exist. Also I’m wary of adding an extra build step in case I forget to do it, and we end up with the next version only being on Github.

Alternatively if there was a desire to pull it into the OS proper and make it part of the hard drive image, I’d be willing to do the dev work for that. The licensing would need to be clarified with the previous developers – that’d be Darren Salt and Oliver Betts for the initial work, but also Jon Abbott and Steve Pampling for their contributions.

Alternatively if there was a desire to pull it into the OS proper and make it part of the hard drive image, I’d be willing to do the dev work for that. The licensing would need to be clarified with the previous developers – that’d be Darren Salt and Oliver Betts for the initial work, but also Jon Abbott and Steve Pampling for their contributions.

There is a desire that it should be part of the OS.

The way is not clear.

We could add a thread to the Wish list forum and kick it around for 10 years or so. Keep fingers crossed that the wish be granted.

Alternatively you could persuade Andrew or Andy to add it to their RISC OS distros.

But PackMan does seem to be a good place for it. It my first port of call for system related software.

but perhaps you should speak to a doctor.

;)

Binary releases expire off of Github after 90 days

Yeah, it’s part of the “live fast and die young” ethos that everybody is trying to promote these days (either that or Constant Integration nonsense). I understand Google’s app store is the same. God forbid somebody make a little app that just works, nope, you gotta keep updating it.

sadly I have no control over this

Perhaps you could stick it into a file with an .ffa extension and call it a resource? Then just tell people to grab that as GitHub is being intentionally annoying.

I didn’t know there was an “adopt Zap” bounty

There isn’t. It’s discussion about the possibility, however I think a major stumbling block might be sorting out a licence with everyone.

Plus, you know, the big wodge of assembler.

Plus, you know, there’s another editor that is being actively maintained, so it’s not as if it’s a choice of only Zap or Edit.

I should point out here that your browser, if it’s any good, will throw big scary warnings for Stefan’s Adopt Zap link because he’s using – for some utterly unknown reason – the .co.uk version of this site, for which the SSL cert does not cover.
(and if your browser didn’t freak out over that, delete it immediately, it’s a piece of poop)

I don’t really want to adopt the whole thing

I’ve been pasting in bits, but I don’t really have the skill set to deal with an editor. It’s one thing “knowing assembler” but quite another rummaging around inside a large program that needs fixed.

Thankfully it’s been a community effort so far, though I must try to dig up the info on that triple-click issue to see about fixing it.

I don’t know how to build Packman packages

Somebody used to have this sort of thing autobuilt as the final part of their MakeFile.

If that’s you, dear reader, would you mind sharing how?

Alternatively if there was a desire to pull it into the OS proper

That would probably be the most logical option, but, as John suggests, don’t hold your breath.

Simplest/quickest to get it pushed into RISC OS Direct etc (if it isn’t already) and go from there.

It my first port of call for system related software.

Mine’s !Store. So there’s that option too. If you don’t have an account there, toss me a zip file of it and I’ll stick it up under my account alongside Zap.

All joking aside – the latest release is 2.77, and the module builds from the BASIC code. You double-click the “Release” obey file, or the BASIC source code, and it produces a module. I’m pretty sure it says this on the Github page.

Someone correct me if I’m wrong, but the key bindings are modifiable, but it would appear that the RebindKeys obey file calls the file named “Rebinder” – except the file is actually called RebindBase

[…] though I must try to dig up the info on that triple-click issue to see about fixing it.

I’ve already provided the fix for the Zap triple-click problem in the adopt Zap thread.

:-)