User feedback:
Line numbering seems to be always relative to 96-line buffer breaks. For example, if I delete 20 lines from the first buffer, then go down until the second buffer loads, the line numbers go from 75 to 96 in one step. In this case also, if I use the ^G go command to go to line 80, it says “line not found”. Maybe this is by design but it makes the line numbers not very useful.
If a command line ^G go or ^F find is pressed and then not needed and then return is pressed without entering anything, the command aborts, but the status line still shows the prompt which might be a little confusing.
User feedback: Line numbering seems to be always relative to 96-line buffer breaks. For example, if I delete 20 lines from the first buffer, then go down until the second buffer loads, the line numbers go from 75 to 96 in one step. In this case also, if I use the ^G go command to go to line 80, it says “line not found”. Maybe this is by design but it makes the line numbers not very useful.
If a command line ^G go or ^F find is pressed and then not needed and then return is pressed without entering anything, the command aborts, but the status line still shows the prompt which might be a little confusing.