... | ... | @@ -38,25 +38,25 @@ commands are shared between "index" and "pager". Yet, to control the |
|
|
same action in both modes with the same key requires that you configure
|
|
|
the key for both separately.
|
|
|
|
|
|
`* bind index K mail`
|
|
|
`* bind pager K mail`
|
|
|
`* bind index K mail`
|
|
|
`* bind pager K mail`
|
|
|
|
|
|
## Tagging: applying a <function> to multiple messages
|
|
|
|
|
|
There are two special commands available in several modes: **tag,
|
|
|
tag-prefix**. With "tag" you select a list of messages to which a
|
|
|
subsequent **built-in** <function> should be applied. As long as you
|
|
|
subsequent **built-in** `<function>` should be applied. As long as you
|
|
|
don't change the mode (or folder in index mode), you may work with
|
|
|
single messages on and off this tagged list before you apply a
|
|
|
<function> to the list. Invoking a <function> as usual applies only to
|
|
|
the currently selected item. If you apply <tag-prefix>, then the next
|
|
|
<function> applies to the whole list\! There is also <tag-prefix-cond>,
|
|
|
which applies a following <function> only of there is a list\! Sometimes
|
|
|
<function> to the list. Invoking a `<function>` as usual applies only to
|
|
|
the currently selected item. If you apply `<tag-prefix>`, then the next
|
|
|
<function> applies to the whole list! There is also `<tag-prefix-cond>`,
|
|
|
which applies a following `<function>` only of there is a list! Sometimes
|
|
|
you might want it to work anyway, sometimes you don't: choose carefully
|
|
|
when to use what.
|
|
|
|
|
|
Also RTFM about "auto\_tag, delete\_untag, print\_split, print\_decode,
|
|
|
pipe\_split, pipe\_decode" for your options how to adjust <tag-prefix>
|
|
|
pipe\_split, pipe\_decode" for your options how to adjust `<tag-prefix>`
|
|
|
behavior.
|
|
|
|
|
|
## Macros
|
... | ... | @@ -64,27 +64,27 @@ behavior. |
|
|
You can combine a sequence of actions with a single keystroke by using
|
|
|
macros. They are defined like regular key bindings, except that they
|
|
|
take not only a single function as argument, but a series of keys or
|
|
|
"<functions>".
|
|
|
"`<functions>`".
|
|
|
|
|
|
You can specify literal keys, which is extremely useful to fill in
|
|
|
dialog input that you normaly enter manually. However, you should limit
|
|
|
literal keys exactly to this purpose of editor input. For the
|
|
|
portability of a macro into the environment of another user's
|
|
|
keybindings it is recommended that you use the "<function>" syntax to
|
|
|
keybindings it is recommended that you use the "`<function>`" syntax to
|
|
|
call actions rather than your currently bound key for that function,even
|
|
|
though it looks more complicated.
|
|
|
|
|
|
`* bad: macro pager K 'c+bla\nm'`
|
|
|
`* good: macro pager K '`<change-folder>`+bla`<enter><mail>`'`
|
|
|
* bad: `macro pager K 'c+bla\nm'`
|
|
|
* good: `macro pager K '<change-folder>+bla<enter><mail>'`
|
|
|
|
|
|
See /Macros for a longer introduction.
|
|
|
See [/Macros](MuttGuide/Macros) for a longer introduction.
|
|
|
|
|
|
## TAB completion in "editor" mode
|
|
|
|
|
|
In every prompt where you have to enter a folder or alias, mutt will
|
|
|
autocomplete a partially given path (item for alias) by pressing the
|
|
|
**TAB** key. This works even with the shortcuts & remote folders (see
|
|
|
/Folders).
|
|
|
[/Folders](MuttGuide/Folders)).
|
|
|
|
|
|
When mutt has reached a point where it can't auto-complete on its own
|
|
|
(no more or too many matches), you can hit **TAB** another time
|
... | ... | @@ -93,7 +93,7 @@ entries matching the given (partial) path. That's the same as "c?" == |
|
|
start with empty partial path. Have a look for "**$mask**" to set
|
|
|
personal filters for files displayed.
|
|
|
|
|
|
Note: if the browsing after "c?" or "c<TAB><TAB>" ends in a
|
|
|
Note: if the browsing after "c?" or "c\<TAB\>\<TAB\>" ends in a
|
|
|
**different** directory than you started, then the internal "browsing
|
|
|
directory" for the **next directory scan** will be set to that **last
|
|
|
browsed directory**. This directory is also used as **current relative**
|
... | ... | @@ -101,9 +101,9 @@ for any file operation **without full path**. The initial "browsing |
|
|
directory" is set to the value of **$folder**. To make sure that you
|
|
|
start out your browsing with the "$folder" base even after changing
|
|
|
dirs, always use "+" or "=" as initial path to be completed\! (see
|
|
|
/Folders)
|
|
|
[/Folders](MuttGuide/Folders))
|
|
|
|
|
|
`c+`<TAB><TAB>
|
|
|
`c+<TAB><TAB>`
|
|
|
|
|
|
When in "folder browser", you can hit '?' to see its specific key
|
|
|
bindings for extra functions. Some of them are only useful and therefore
|
... | ... | @@ -111,7 +111,7 @@ available with IMAP enabled. Others are generally useful, like going to |
|
|
"mailboxes" list, which is bound to <TAB> by default: to get there from
|
|
|
the start you have to hit
|
|
|
|
|
|
`c?`<TAB>` or c`<TAB><TAB><TAB>
|
|
|
`c?<TAB>` or c`<TAB><TAB><TAB>`
|
|
|
|
|
|
## generic Movement
|
|
|
|
... | ... | @@ -120,63 +120,62 @@ for the list of functions, you'll notice a lot of functions with "next-" |
|
|
and "previous-" in
|
|
|
them:
|
|
|
|
|
|
`page, line, thread, subthread, new, unread, new-then-unread, undeleted, entry`
|
|
|
`page, line, thread, subthread, new, unread, new-then-unread, undeleted, entry`
|
|
|
|
|
|
Most important to remember is the distinction between "undeleted" and
|
|
|
"entry", so that you can move to marked as deleted messages, which
|
|
|
normally are jumped over.
|
|
|
The difference between "unread" and "new" is that if instructed via
|
|
|
**$mark\_old**, then mutt will mark new but yet unread messages as "old"
|
|
|
when you leave the folder. See /Index.
|
|
|
when you leave the folder.
|
|
|
|
|
|
At last, of course you have absolute movement,
|
|
|
too:
|
|
|
|
|
|
`* jump to specific number simply by entering it.`
|
|
|
`* jump to top, bottom, middle of page, first/ last entry of list.`
|
|
|
`* scroll current message to top, bottom, middle of screen.`
|
|
|
* jump to specific number simply by entering it.
|
|
|
* jump to top, bottom, middle of page, first/ last entry of list.
|
|
|
* scroll current message to top, bottom, middle of screen.
|
|
|
|
|
|
### special system commands
|
|
|
|
|
|
`* ":" let's you enter a muttrc cmd to be executed once (useful "`**`:set``
|
|
|
``?var`**`" to see current value)`
|
|
|
`* "!" invokes a command-shell, returns to mutt when you exit the shell`
|
|
|
`* quit: end mutt after saving changes to current folder`
|
|
|
`* exit: end mutt `**`without`**` saving changes to current folder`
|
|
|
`* create-alias, edit current message, `
|
|
|
* ":" let's you enter a muttrc cmd to be executed once (useful "**`:set
|
|
|
?var`**" to see current value)
|
|
|
* "!" invokes a command-shell, returns to mutt when you exit the shell
|
|
|
* quit: end mutt after saving changes to current folder
|
|
|
* exit: end mutt **without** saving changes to current folder
|
|
|
* create-alias, edit current message,
|
|
|
|
|
|
## Index + Pager mode
|
|
|
|
|
|
### folder management
|
|
|
|
|
|
See also
|
|
|
/Folders.
|
|
|
See also [/Folders](MuttGuide/Folders).
|
|
|
|
|
|
`* un-/delete $save_empty`
|
|
|
`* flags`
|
|
|
`* auto_tag, tagging, prefix,`
|
|
|
`* simple_search, `<limit>` cmd, patterns list (+ [PatternQuoting](PatternQuoting))`
|
|
|
`* save: confirmappend, confirmcreate`
|
|
|
`* save /copy /move (see [MuttFaq/Action](MuttFaq/Action))`
|
|
|
`* change: delete, move`
|
|
|
* un-/delete $save_empty
|
|
|
* flags
|
|
|
* auto_tag, tagging, prefix,
|
|
|
* simple_search, `<limit>` cmd, patterns list (+ [PatternQuoting](PatternQuoting))
|
|
|
* save: confirmappend, confirmcreate
|
|
|
* save /copy /move (see [MuttFaq/Action](MuttFaq/Action))
|
|
|
* change: delete, move
|
|
|
|
|
|
### msg management
|
|
|
|
|
|
`* view (src or MIME) -> /Attachments "pager" + "attach" mode`
|
|
|
`* auto_view, $forward_decode`
|
|
|
`* pipe_sep, pipe_split, print_*`
|
|
|
`* toggle weeding, toggle quoted, skip quoted: quote-regexp`
|
|
|
* view (src or MIME) -> /Attachments "pager" + "attach" mode
|
|
|
* auto_view, $forward_decode
|
|
|
* pipe_sep, pipe_split, print_*
|
|
|
* toggle weeding, toggle quoted, skip quoted: quote-regexp
|
|
|
|
|
|
### get/ check new mail
|
|
|
|
|
|
`* [MuttFaq/Folder](MuttFaq/Folder) -> mailcheck, timeout`
|
|
|
`* pop internal, URL ...`
|
|
|
* [MuttFaq/Folder](MuttFaq/Folder) -> mailcheck, timeout
|
|
|
* pop internal, URL ...
|
|
|
|
|
|
## Compose msg
|
|
|
|
|
|
`* mail, reply (group, list) -> /Compose "alias", "compose", "query", "postpone", "pgp" + "attach" mode`
|
|
|
`* bounce, resend,`
|
|
|
`* forward: various mime_* + forward_* vars`
|
|
|
* mail, reply (group, list) -> /Compose "alias", "compose", "query", "postpone", "pgp" + "attach" mode
|
|
|
* bounce, resend,
|
|
|
* forward: various mime_* + forward_* vars
|
|
|
|
|
|
As long as $mime\_forward is unset (the default), attachments will be
|
|
|
automatically inserted into the body of the message. On the other hand,
|
... | ... | |