I would like to clarify some of my questions

On Thu, Nov 18, 1999 at 11:24:04AM -0600, Dan Lipofsky wrote:
> I have been using mutt for a few days and have quite a list of questions
> I would appreciate help with.  I am using Mutt 1.0i on a RedHat 6.1 Linux
> 2.2.12 machine with IMAP.  I downloaded it as mutt-1.0i-2.cfp.rhl6.i386.rpm.
...
> Is there a way to get a list of the current key bindings, broken down
> by map (i.e. generic, index, browser, etc)?

There are several maps.  Generic seems to apply to most modes,
plus there is a mode dependent map.  It would be nice to know
whether the binding came from the generic map or the mode
dependent map.  This would quickly help me learn which functions
applied to which modes w/o having to RTFM.  For those kind enough
to mention it, I did RTFM, and it was the FM that prompted me
to ask the above question about key bindings broken down
by map.  I didn't read every page, so I didn't see section 6.4
wich probably gives me most of the info I need.  So shoot me.

It would probably be a good idea to provide a link from
the key bindings section of the manual to the functions section.
I still think the feature I was hoping existed would be a good idea.

> Is there a way I can get a description of what a key is currently
> bound to (like C-h k <key> in emacs)?

I do realize I can hit '?', but I was hoping for a function that
returns the binding for just the one key I hit.  Two reasons:
1) I wouldn't have to scan the list
2) Very useful for debugging.  For example, my home and end keys
   are not working.  It would be nice to see what key sequence
   is actually reaching Mutt when I hit one of these keys.
   The message could say something like
        ... is bound to fff
   or
        ... is not bound to any function
   This would allow me to see what ... is.  This is what emacs does.

> Is there a way to see my current list of aliases?

Several people said just look at you alias file.  Well, I can do that,
but I see there is an alias_format variable, which the manual claims
"specifies the format of the data displayed for the `alias' menu".
So I assume there must be some way to call up the alias menu.

> When new mail arrives, the index does not scroll down to show the new
> mail.  It would be nice if it did.  It would also be nice if it showed
> all the new mail on startup (if it fits on the screen).  Currently it
> tends to just show the first line.

When new mail arrives, I get a message saying "New Mail" at the bottom
of the screen.  But all I actually see in the index are my old messages,
because the new ones are off the bottom of the page.  It would be useful
to have mutt autoscroll to bring new messages onto the screen so that
I could tell at a glance if I wanted to bother with the message.

Also, suppose I start up mutt and my inbox has 200 old and 20 new messages,
and my window allows me to display 40 lines.  Mutt shows me messages
161-201, all but one of which is old, when I start up.  I would rather
it show 180-220, i.e. show me all the new messages (if possible) and
as many of the old messages as possible.

Thanks,
Dan

Reply via email to