Go to screen top/bottom
Go to screen top/bottom
"go to screen top" (Ctrl+PgUp) moves the caret to the left-most visible column of the top-most visible line, and "go to screen bottom" (Ctrl+PgDn) moves the caret to the left-most visible column of the bottom-most visible line. In other editors (including SynWrite), those functions move the caret to the top/bottom visible line, while retaining the current column, which I think is more standard. However, I can see value in both ways, and imagine that some like it the way it is. Perhaps there could be two pairs of functions, one which keeps the caret column, and one which moves the caret column? Or, perhaps there could be a setting, whether or not to change the column in those functions?
-
main Alexey
- Posts: 2265
- Joined: 25.08.2021 18:15
Editors which behave the way I described:
ConTEXT
Notepad++
PSPad
RJTextEd
SynWrite
Textadept
That's all I presently have to test with. All of the above editors have those two functions assigned to the Ctrl+PgUp and Ctrl+PgDn keys, with the exception of Notepad++, which by default has no hotkeys assigned to those two functions, and I had to go searching for them: they are called SCI_STUTTEREDPAGEUP and SCI_STUTTEREDPAGEDOWN, which are Scintilla functions. Note that Textadept is also based on Scintilla, but has the keys assigned by default. I have not tested any editors which behave like CudaText, however I seem to have a dim recollection of seeing that behaviour somewhere before, and I think it is a legitimate behavior, but one which should be selected by the user, either by an option, or by a second pair of functions, as both are useful.
EDIT: It is important to note that this behaviour is effective when editor is in the mode which allows caret to move past end of line, sometimes called virtual space, free caret/cursor, etc., and all of the above editors were tested in that mode, as of course was CudaText. That is the only mode which I use, and I reject editors which do not have or allow that mode, but restrict the caret/cursor to be within the line. In some (most?) of the above editors, that mode is optional, i.e. the editor allows either mode by user selection.
ConTEXT
Notepad++
PSPad
RJTextEd
SynWrite
Textadept
That's all I presently have to test with. All of the above editors have those two functions assigned to the Ctrl+PgUp and Ctrl+PgDn keys, with the exception of Notepad++, which by default has no hotkeys assigned to those two functions, and I had to go searching for them: they are called SCI_STUTTEREDPAGEUP and SCI_STUTTEREDPAGEDOWN, which are Scintilla functions. Note that Textadept is also based on Scintilla, but has the keys assigned by default. I have not tested any editors which behave like CudaText, however I seem to have a dim recollection of seeing that behaviour somewhere before, and I think it is a legitimate behavior, but one which should be selected by the user, either by an option, or by a second pair of functions, as both are useful.
EDIT: It is important to note that this behaviour is effective when editor is in the mode which allows caret to move past end of line, sometimes called virtual space, free caret/cursor, etc., and all of the above editors were tested in that mode, as of course was CudaText. That is the only mode which I use, and I reject editors which do not have or allow that mode, but restrict the caret/cursor to be within the line. In some (most?) of the above editors, that mode is optional, i.e. the editor allows either mode by user selection.
-
main Alexey
- Posts: 2265
- Joined: 25.08.2021 18:15