BASIC screen editor

[skywalker]

BASIC files can of course be edited in GUI editors, but BASIC itself has a rather cute screen editor available via the EDIT command - useful for quick hacks/experiments.

I find the editor to be rather nice, but it seems to suffer from some integration issues with the GUI around it:
- If you start a BASIC session in a task window, then the screen editor doesn't work properly. It looks like various terminal cursor operations don't work in windowed mode and you get strangely placed text and strange characters (possibly the cursor/terminal control characters being printed?).
- If you use F12 to get the global ShellCLI, start a BASIC session, then start the screen editor (EDIT), the editor works nicely, but upon leaving the editor and the CLI (i.e. return on empty line at * prompt), the screen is left in a very low resolution/low colour mode. It would be nice if exiting the CLI would cause the GUI to reset the screen settings to those that were active when the CLI was entered.

Now, these may be bugs, or intentional (for some reason). Perhaps though there's some lore about how to use these so the issues can be avoided?

[jackokring]

This could be made a temporary issue. The question becomes "why does one OS become incompatible with another at such a BASIC level?". BBC basic is fine. I prefer a PROC <name> calling convention as procedure names only creates type issues. <name> on it's own should perhaps behave as the string of the code. The A in BASIC says it all. ALL purpose. The dream has still not become the reality.