The BEST QL Editor

[RalfR]

The most annoying thing IMHO is that uEmacs warps the pointer to some unexpected place if you select a menu item. I keep searching my mouse pointer in that program.

Isn't it similar in QD? When you click on an item with the mouse from the editing window, you first have to look back at where you were and put the pointer there again.

[pjw]

The most annoying thing IMHO is that uEmacs warps the pointer to some unexpected place if you select a menu item. I keep searching my mouse pointer in that program.

Isn't it similar in QD? When you click on an item with the mouse from the editing window, you first have to look back at where you were and put the pointer there again.

Not if you WAKE QD, either via a wake hotkey or by DOing the window if partially buried. Also, I find the sprite cursor easier to see than the traditional one.

QD is great, though there are a few bugs and niggles. A pity it wasnt developed further.

The only other editor I use is DP's The Editor, special addition. It doesnt do macros, as in recording keystrokes and playing back keystrokes, but it is programmable, so I often use it for cleaning up code or text that comes from other worlds.

Full disclosure: My setup is SMSQ/E in high colour and a large screen and more memory than I normally ever need. On a BBQL Id probably use something like Jan Bredenbeek's QED. On a QL with 512Kb+, The Editor. With PE, QD.

[RalfR]

The most annoying thing IMHO is that uEmacs warps the pointer to some unexpected place if you select a menu item. I keep searching my mouse pointer in that program.

Isn't it similar in QD? When you click on an item with the mouse from the editing window, you first have to look back at where you were and put the pointer there again.

Not if you WAKE QD, either via a wake hotkey or by DOing the window if partially buried.

I meant a menu item of QD, not outside QD.

[tofro]

The most annoying thing IMHO is that uEmacs warps the pointer to some unexpected place if you select a menu item. I keep searching my mouse pointer in that program.

Isn't it similar in QD? When you click on an item with the mouse from the editing window, you first have to look back at where you were and put the pointer there again.

Nope. If you click on a menu item in QD2 (or any other reasonably behaving PE program), the pointer stays where it is. If you do the same in µEmacs, it can be just about anywhere but not where you expect it to be.

[RalfR]

Hmm, if I move the pointer (cursor pointer) in QD to the menu bar, it disappears from the text, so how do you remember where it was?

[desin]

place the cursor with the mouse
use the shortcuts F x, CF x ,Shift x for commands

Markus

[RalfR]

Well, then menu items that can be clicked with the mouse don't really make much sense.

[ql_freak]

The most annoying thing IMHO is that uEmacs warps the pointer to some unexpected place if you select a menu item. I keep searching my mouse pointer in that program.

Isn't it similar in QD? When you click on an item with the mouse from the editing window, you first have to look back at where you were and put the pointer there again.

I do not understand what you both are meaning. Here after a command the mouse pointer is invisible and the text cursor is either at the same position (e.g. if you abort with ^G) or in the Emacs command line, if further arguments are required or at the position where it would be if you entered the command via a shortcut (key binding) or executing a command without the menu system.

For me the most annoying is, that you cannot kill the current buffer, you first have to switch to another buffer. But I think it should be possible to write a macro which allows closing the current buffer. I will have a look, when I have finished my reflection toolkit.

[RalfR]

We just spoke about QD .

[ql_freak]

The best QL editor/IDE might have the following features:

Doesn't need line numbers
Automatic indent, configurable. 2, 3, 4 spaces. 240x75 that'll be useful
...

It should be possible to implement a lot (most?) of your wishes with the MicroEmacs builtin programming language. It is a full blown programming language (better than the macros of The Editor and even better than the programming capabilities of DME) with a lot of inbuilt variables which can be read and (mostly) written to.

Have you tried to use abbreviations (you must add the mode abbrev to the buffer if you want to use them)?