Tue 02 May 2017 07:28:00 PM UTC, comment #1:
> but when there is no match, or when you move away from the
> match, should it still be visible then?
Good point. When there is no match, the cursor certainly shouldn't be shown, as it distracts from the message on the status bar. And when moving around after having searched... yes, it would be most consistent to switch the cursor back off again.
|
Tue 02 May 2017 05:11:34 PM UTC, original submission:
In current git (3d1ef8e), the cursor is supposed to be invisible while in the help browser, but certain circumstances can leave it visible, and not all of them may be desirable. These circumstances can be reproduced as follows (assuming an en_US locale):
Scenario 1:
1. Start nano, and press Ctrl-G to enter the help browser.
2. Press Ctrl-W in the help browser, and enter "replace" at the search prompt. The cursor will become visible, and end up at the first character of the first instance of "replace".
Scenario 2:
1. Start nano, and press Ctrl-G to enter the help browser.
2. Press Ctrl-W in the help browser, and enter "xyzzy" at the search prompt. The cursor will become visible, but remain where it was, since "xyzzy" occurs nowhere in the help text.
In either case, the cursor still remains visible when you move vertically via Up, Down, PageUp, PageDown, Meta-\ or Meta-/ after searching. However, it becomes invisible again when you press (for example) Left or Right, after nano displays the "Unbound key" warning. Having the cursor be visible when you successfully find a match may be desirable, since it draws attention to the match, but when there is no match, or when you move away from the match, should it still be visible then?
|