GNU nano - Bugs: bug #47194, doing a Ctrl+Right on the last...
You are not allowed to post comments on this tracker with your current authentication level.
bug #47194: doing a Ctrl+Right on the last onscreen word sometimes scrolls too much
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Thu 18 Feb 2016 08:31:38 PM UTC | ||
Severity: | 2 - Minor | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Thu 07 Apr 2016 12:30:38 PM UTC, comment #3: |
Benno Schulenberg <bens> |
Wed 06 Apr 2016 07:51:55 PM UTC, comment #2: Ah, I shouldn't have said three lines. It scrolls again two lines when in that situation just one line would have been enough. |
Benno Schulenberg <bens> |
Wed 06 Apr 2016 07:49:03 PM UTC, comment #1: To reproduce, do 'stty rows 24 && src/nano +22 README', then type nine times <Down>, until the cursor is on the line that says "make install". Then type three times <Ctrl+Right>. The screen scrolls two lines to bring "It's that simple" into view. That is the expected behavior.
|
Benno Schulenberg <bens> |
Thu 18 Feb 2016 08:31:38 PM UTC, original submission:
As noted already in bug #42645, when the cursor is on the last word of the screen, and there are one or more blank lines shown below this last word, then a Ctrl+Right will scroll one or more lines too many -- too many in the sense that it is not necessary to scroll those lines in order to show the next word. So it shouldn't. |
Benno Schulenberg <bens> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-06-20 | bens | Open/Closed | Open | Closed | |
2016-04-07 | bens | Status | None | Fixed | |
Assigned to | None | bens |
Powered by Savane 3.13-f8d8.
Corresponding source code
Fixed in git, cb17732a.