Ticket #2807 (new defect)
pager.c remembers TopLine when it shouldn't
| Reported by: | tamo@… | Owned by: | mutt-dev |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.0 |
| Component: | mutt | Version: | 1.5.14 |
| Keywords: | #2118 | Cc: | SHIOZAKI Takehiko <st@…> |
Description (last modified by myon) (diff)
Since this change (http://mutt.kublai.com/hg/cvs/rev/b894fd4c9032) on Sep 08 2005, the builtin pager keeps its position even on OP_MAIN_NEXT_UNDELETED. So you cannot re-read the last message from the top of it with <space>. (See How-To-Repeat) This must be a side-effect of http://bugs.mutt.org/1210 >How-To-Repeat: 1. :unset pager_stop 2. <change-folder> to a folder which has a long (more than a screen-length) message as the last entry. 3. Hit <space> on the last message. 4. Repeat <space> until the message finishes. 5. You will be in index mode (because the message is the last entry in the folder). 6. Hit <space> again. You will see the _bottom_ of the message, not the top. >Fix: Forget TopLine when <next-page> (with $pager_stop) causes OP_MAIN_NEXT_UNDELETED. (though Brendan called it "a bogus detection")
Change History
Note: See
TracTickets for help on using
tickets.
