bugGNU nano - Bugs: bug #63008, when specifying only a column...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #63008: when specifying only a column number, the line should not be centered

Submitter:  Benno Schulenberg <bens>
Submitted:  Sun 04 Sep 2022 07:49:10 AM UTC
   
 
Severity:  2 - Minor Status:  Fixed
Assigned to:  bens Open/Closed:  Closed

Sun 04 Sep 2022 08:54:38 AM UTC, comment #1: 

Fixed in git, commit 40b9e68e, by keeping the cursor stationary when the answer began with a comma.  (This is ugly because it doesn't allow the comma to be preceded by blanks, and doesn't work when the user mistyped and typed a period instead of a comma.  But... for the vast majority of cases, it will do.)

Benno Schulenberg <bens>
Group administrator
Sun 04 Sep 2022 07:49:10 AM UTC, original submission:  

To see what I mean, run:

src/nano --ignore -x +117 README

See that the cursor is seven rows from the bottom of the screen.
Now go to column 66 by typing: M-G ,66 <Enter>
See that the current line has jumped to the center of the screen.  This is unnecessary.  It would be better, when the user specifies only a column number, that the current line stays where it is on the screen and that only the cursor moves to the requested column.

(The above case is not very distracting, because the cursor is near the end of the file, and the resulting blank part of the screen shows that.  But if you're somewhere in the middle of a file, the current line jumping to the center of the screen can be  quite disorienting, especially when the surrounding paragraphs look similar.)

Benno Schulenberg <bens>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by bens (Submitted the item)
  •  

    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 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-11-16 bens Open/ClosedOpen Closed
    2022-09-04 bens StatusNone Fixed

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code