Re: [PATCH] menu_context (was: Re: index_context: like pager_context)
Hello Christoph,
On Saturday, March 6, 2004 at 3:26:13 PM +0100, Christoph Berg wrote:
> I've written an improved version of Mike's index_context patch (that
> is now called menu_context to be consistent with $menu_scroll)
Great thanks!
> The new $menu_move_off option controls whether the menu entries are
> allowed to move off from the bottom of the menu.
Good option. But there is a little glitch in case:
| set menu_scroll menu_move_off menu_context=7
...and the index has near as much total lines as are visible. Say on
a 80x25 term you have 22 visible lines, and you <limit>~m-22<enter>. Now
move down indicator with <next-entry>, <next-undeleted> or such. When
indicator reaches near bottom, display begins to jump up and down.
BTW here is an extract of a mail to Mike: It may be of interest, and
the little problem reported is still valid for menu_context.6
| There is an annoying interaction with page jumps near top of index:
| Like with $index_context=7 and $menu_scroll=yes do a <first-entry>
| then <next-page><previous-page> in index: You should see top page
| again, say lines #1 to #34. But you see lines #8 to #41.
|
|
| More generally, I wonder if it would be possible or interesting to
| have $index_context act on scrolls (line by line), but still have full
| page jumps, perhaps with 0 or 1 line of context. Or *another* variable
| to set lines of context in page jump case. The indicator would still
| be placed $index_context lines from bottom of next page, but the said
| page would be fully new.
|
| I'm not sure, but seem to have understood that's this very effect on
| page jumps that caused not inclusion in Mutt... Source: Discussion by
| Michael Elkins on mutt-dev, msgid <20020329183608.GA3064@xxxxxxxxxxx>.
Bye! Alain.
--
Give your computer's unused idle processor cycles to a scientific goal:
The Genome@home project at <URL:http://genomeathome.stanford.edu/>.