Hello, On Fri, 11 Oct 2002 00:33:22 +0200, Michael Tatge <[EMAIL PROTECTED]> said: > Susan Kleinmann ([EMAIL PROTECTED]) muttered: > > I saw something that showed what mutt command could > > be used to get a list of all the key bindings that were active in the > > current menu. > > Try the magic '?'. > > Michael [wondering wheather Susan's help bar looks diffenrent to his one]
Thanks to all for your help on "help". I deserve a big "duh" for this. I guess I was looking for some key which would either show a compact table of keys that were already defined, or, if there were lots of pre-defined keys, then some key which would show a short list of the keys that were not yet defined. I must still be doing something wrong: I can't believe that every single person who uses mutt has to cut and paste all 3 or 4 help screens into an editor, then do a bunch of editing, just to find out which few keys are available to assign to macros. I also can't believe that users are really restricted to single keystrokes to identify macros. Here are a couple of specific ambiguities in the manual: Section 3.3 says that the key to which a function can be mapped may consist of: ... <f1> <f10> Some messages in the mutt-users archives implies that the above really means: <f1>...<f10> Section 3.2 in the manual says that one can define aliases using alias key address [, address, ...] but then says aliases can be used to map "a short string" to a full address. So is "key" to be understood as "a short string" in all cases? or just in the case of aliases? (When Sven answered that he uses various characters as macro "lead-in's", it struck me that mutli-key macros must indeed be possible.) But if "key" is to be understood as "short string" for macros as well as for aliases, then how does the command parser know when the beginning of a short string has been entered, as opposed to a series of individual commands? Sorry for the verbosity -- I'm just trying to be clear about what's causing confusion. TIA, Susan
