bugGNU nano - Bugs: bug #50657, in current git, typing M-= on an...

 
 

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

bug #50657: in current git, typing M-= on an overlong top line causes a Badness warning

Submitter:  Benno Schulenberg <bens>
Submitted:  Mon 27 Mar 2017 05:38:37 PM UTC
   
 
Severity:  3 - Normal Status:  Fixed
Assigned to:  bens Open/Closed:  Closed

Mon 27 Mar 2017 05:51:48 PM UTC, comment #2: 

Sorry, I goofed in the commit message: it should have said scrolling forward first, and scrolling backward second.  :|

It /is/ confusing, the viewport moving one way and the text another.  Normally I refer to the viewport: forward is down -- it is what happens when you use the <Down> cursor key.  Backward is up -- what happens when using the <Up> cursor key.

Benno Schulenberg <bens>
Group administrator
Mon 27 Mar 2017 05:46:41 PM UTC, comment #1: 

Fixed in git, 9cf98070.

And closing because unreleased.

Benno Schulenberg <bens>
Group administrator
Mon 27 Mar 2017 05:38:37 PM UTC, original submission:  

(This is a rereport of comment #9 on bug #50621.)

To reproduce, run:

  stty cols 60 && src/nano --ignore +,77 NEWS

Then type M-= a few times.  Every time there is badness warning.

This happens because when scrolling forward, nano assumes the cursor is somewhere near the bottom of the screen and it is possible to redraw the line that the cursor was on.  When the cursor is on the top line, however, (and using scroll only) this is obviously not the case.  So... avoid redrawing the prior line when current_y is zero, or when current_y is editwinrows minus one.

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
    2017-03-27 bens StatusIn Progress Fixed
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code