StrongED 4.69f9 released

As for throwback – it’s incredibly useful. For example, StrongED’s source is split into 33 (BASIC assembler) files.

Basalt currently has 274 – I could not do that without throwback. ;-)

You cannot edit that bytecode directly

Writing this brought up memories of the ZX Spectrum, where you did effectively edit the bytecode using the single-key entry system. I would not return there.

There’s been another release of StrongED 4.69f9 to fix a few more bugs. http://www.stronged.iconbar.com/archives/releases/se469f9.zip

If you already have StrongED 4.69f9, an update can be found here: http://www.stronged.iconbar.com/archives/releases/up469f9.zip

Changes from the previous 4.69 (31-01-2016) release:

• If a List-of-Found was configured to highlight matches in the text then an abort would occur. This affected LoFs with spelling mistakes mostly as these have the highlight option on by default.
   
• Highlighted matches could fail to redraw correctly under certain conditions, such as dragging another window over the text.
   
• Attempting to edit BASIC programs that had been compacted often resulted in a non-working version after saving. StrongED can be configured to add spaces when detokenising a BASIC file to prevent errors when the file is retokenised. The option for this is on by default but due to a bug it wasn’t being obeyed.
   
• There have been a few tweaks to the manual as well. A page on displaying line numbers has been added to the Introduction section. The section on advanced search has been brought in line with the 4.70 manual. Various little corrections.

As always, all feedback is welcome and appreciated!

I notice when entering a new line in BASIC mode, the permission window pops up, I guess I could just use my old config, but if you could refresh my memory how to fix that please.

I have been using a mac keyboard with my Iyonix for a while. It is the clear type with a concave top and two sideways usb ports.
The only key that was odd was the = key on the numeric keypad, it was outputting #. I have it swapping with the key swap module but is there alternative keyboards that can be configured?
I think StrongEd base mode already sets the DEL key to <4> for ‘forward delete’ and I set this in Taskwindow mode also. Maybe it could be set globally on all modes? or is it up to a mode contributor to set these things?
I have been logging into a PiZero/FreeBSD which uses csh. I may be able to get arrow key responses by setenv EDITOR emacs (instead of vi), fingers crossed. I also need to configure it to turn off the escape sequences it sometimes sends sometimes doesn’t. Backspace on a space is OK but on a alphabet char it deletes but also sends [K and repeat dels they overlap like [[[[[K

I notice when entering a new line in BASIC mode, the permission window pops up,

The BASIC mode is configured to perform a number of actions when Return is pressed.

• Ensure that keywords are in uppercase
• Apply smart indentation to the line
• Insert a newline character

Casting keywords to uppercase is done by running a small add-on and it is the ‘Process’ function that triggers the permission window (so that you’re aware that external code is being called).

When you click ‘Allow action’ then you can see what it does. If you’re happy with the result, you can click ‘Allow always’ next time and the action will be carried out in future without being asked for permission.

If the result is not to your liking then there are two ways to deal with it. Click on ‘Deny always’, this will permanently disable the Process function (in BASIC mode). The down side of this is that it may also block Process based actions that you do want to use.

The other way to deal with this is to alter the functions tied to the Return key so that it does what you want. Removing the Process function would stop the permission window being triggered, but keywords are then not uppercased.

I think StrongEd base mode already sets the DEL key to <4> for ‘forward delete’ and I set this in Taskwindow mode also.

Default StrongED ties the DeleteRight function to the Delete key, it does not map it to another keycode. TaskWindow mode is different as most keys are passed on to the underlying task.

You can change the keycode sent to a TaskWindow task by using the CharsToBuffer function, as you’ve already found.

Maybe it could be set globally on all modes? or is it up to a mode contributor to set these things?

If you want to have it set up globally then you’ll need to edit BaseMode. This will make it available in all modes (as long as they don’t override it).

I doubt whether it would be useful though. It would just trigger whatever is tied to Ctrl-D (<4>) in a mode (or BaseMode).

Thanks for the explanation on BASIC mode, I’ll keep a copy in my store directory, along with the program archives.
Ctrl-D is interesting when logged into FreeBSD, it works as forward delete until there is no more to delete, then uses it as an exit from the next layer(s) of shell all the way from a running program (linux typically uses Ctrl-C there) through to logging out.
I found all the arrow keys /do/ work as expected, so I am 100% functional, just have to put a stop to the extra escape codes being sent back. Other programs output color codes to a point it is unreadable, so it is something that needs globally turning off in FreeBSD, !Convtext could be set up to convert a captured screen of output if push comes to shove.
My editting consists of using cat(unix) in both directions until I install something I know better than ed or vi.