On Tue, Nov 30, 1999 at 09:13:27AM +0000, Chris Green wrote:
> 1 - "generic" macros rarely seem to work as expected, this may well be
> for valid (but obscure) reasons. Maybe it would be a good idea for
> the manual to point out that index and pager macros are more likely to
> get the required effect.
I was trying to write a generic macro (actually I think it was a
binding) to make <Space> do next-page, rather than write separate
ones for the browser and index screens.
It seemed to work after I rewrote .muttrc and re-sourced it, but
then after leaving mutt and restarting it, it stopped working. I
wonder if this was connected to what the manual says about
changing settings:
> The generic menu is not a real menu, but specifies common
> functions (such as movement) available in all menus except for
> pager and editor. Changing settings for this menu will affect
> the default bindings for all menus (except as noted).
I never saw any of these promised 'as noted' messages, but I had
other macros or bindings of <Space> (or there is a default
binding which views the file (or mailbox) in the browser, which I
can't find in the list in 6.4 in the manual at the moment), and
these were I think the reason my generic binding wasn't working.
I think generic bindings will only work if the key isn't used
for a macro or binding anywhere else.
Is the logic somewhat like that of folder-hooks not being reset,
but in the case of bindings, there is no looking at what is in
.muttrc again? That is the feel I got for it, anyway.
--
Greg Matheson genius + soul = jazz
Chinmin College, Taiwan Mr_Bean on SchMOOze
[EMAIL PROTECTED] & telnet://health.acor.org#8888
