How to Turn Off the Positioning at the Last Cursor Position?

[Arthur]

I can see by default, Zeus remembers the last cursor position and when I move to the next line (regardless whether it is populated or not) it would place the cursor at that last known position. This irritates me. I would like to know how to turn this feature off.
As a side note: the way to End key moves the cursor does not make logical sense to me. E.g. at times it would jump the the end next line and then straight to the end of the file. IMHO it should go to the end of each line until the EOF.

[jussij]

I can see by default, Zeus remembers the last cursor position and when I move to the next line (regardless whether it is populated or not) This irritates me.

Yep. This is standard Brief virtual whitespace behaviour. As a long time Brief user I love it

I would like to know how to turn this feature off.

These sorts of things should be easy to fix since they just represent an entry in the current keyboard mapping and to fix it you just need to re-bind the up and down keys.

To find out what key is being called I recommend doing this:

1) Start macro recording
2) Hit the line up, line down keys
3) Stop macro recording
4) Macros, View source code

You can now see what function is bound to what key which will help when you come to editing the current keyboard map.

Now Zeus has the following move line down alternative keyboard functions that you can choose from:

Code: Select all

MoveLineDown
MoveLineDownEx
MoveLineDownAndFirst
MoveLineDownAndLast
MoveLineEnd
MoveLineFirst

You can test out the behaviour of these keyboard by opening the Macros, Execute Script dialog and directly typing in the function name.

But that is not all.

If none of these are suitable it should also be possible to create a macro and then bind that macro to the key.

So in theory any desired behaviour should be possible.

As an example take a look at the backspace.lua macro.

As a side note: the way to End key moves the cursor does not make logical sense to me. E.g. at times it would jump the the end next line and then straight to the end of the file. IMHO it should go to the end of each line until the EOF.

This sounds like the standard Brief End key behaviour.

Using the same trick from above you can find out what type of function the End key is running.

If it is running the MoveDocumentEndEx function then that is the standard Brief behaviour for the End key.

Cheers Jussi