Re: mutt/2019: menu_context itches (Re: your mail)
Hi Tamotsu-san,
On Thursday, August 11, 2005 at 10:49:47 AM +0900, Tamotsu Takahashi wrote:
> I've made a [patch-1.5.9.tamo.menu_onlybug.1-extra] to (hopefully)
> correct "<last-entry>" and "opening a box".
Reviewing 1.5.10 + tamo.menu_onlybug.1 + tamo.menu_onlybug.1-extra.
Two things:
· In $menu_scroll=no mode, extra introduces a discrepency between
<last-entry>/box open and all other movements of the same type. Example
say the last entry is the only to have the word "blah" in subject, if
you do a <search>~sblah<Enter>, you see 41-41c41. You should probably
see 35-41c41 as with <last-entry>. I'd like to hear opinion of
no-scrollers though.
Brendan? Are you really here? Brendan? We can hear you: Commit one
patch for "yes", two patches for "no"... ;-)
· In $menu_scroll=yes mode, extra perturbates <last-entry>/box open in
a very illogical way. IMHO the previous "cursor pushes boundaries"
behaviour should be retained.
Summary: I think all cursor movements over entries leading to a
screen repositioning should behave consistently in a given mode. Integer
pages in no-scroll, pushed boundary in scroll mode.
Bye! Alain.
--
KW> Program received signal SIGSEGV, Segmentation fault.
I'm not really here, but also try nuking your header cache.
-- BC in "Real Programmers Don't Eat Cache on Holidays" --