* mu4e: small tweaks to the manual

This commit is contained in:
djcb 2013-06-12 10:09:19 +03:00
parent 8d3e33e476
commit b57ae66605
1 changed files with 22 additions and 14 deletions

View File

@ -732,7 +732,7 @@ respectively. In the example, we use @code{:human-date}, which shows when the
time when the message was sent today, and the date otherwise. time when the message was sent today, and the date otherwise.
@item The header field used for sorting is indicated by ``@t{V}'' or @item The header field used for sorting is indicated by ``@t{V}'' or
``@t{^}''@footnote{or you can use little graphical triangles; see variable ``@t{^}''@footnote{or you can use little graphical triangles; see variable
@code{mu4e-use-fancy-chars}}, indicating the sort order (descending or @code{mu4e-use-fancy-chars}}, corresponding to the sort order (descending or
ascending, respectively). You can influence this by a mouse click, or ascending, respectively). You can influence this by a mouse click, or
@key{O}. Not all fields allow sorting. @key{O}. Not all fields allow sorting.
@item Instead of showing the @t{From:} and @t{To:} fields separately, you @item Instead of showing the @t{From:} and @t{To:} fields separately, you
@ -757,7 +757,7 @@ u=@emph{unread}. The tooltip for this field also contains this information.
Jamie Zawinski's mail threading algorithm, Jamie Zawinski's mail threading algorithm,
@url{http://www.jwz.org/doc/threading.html}}. @url{http://www.jwz.org/doc/threading.html}}.
@item The headers view is @emph{automatically updated} if any changes are @item The headers view is @emph{automatically updated} if any changes are
found during the indexing process, and if there is not current found during the indexing process, and if there is no current
user-interaction. If you do not want such automatic updates, set user-interaction. If you do not want such automatic updates, set
@code{mu4e-headers-auto-update} to @code{nil}. @code{mu4e-headers-auto-update} to @code{nil}.
@end itemize @end itemize
@ -1134,8 +1134,8 @@ is used for images.
@section Displaying rich-text messages @section Displaying rich-text messages
@t{mu4e} normally prefers the plain-text version for messages that consist of @t{mu4e} normally prefers the plain-text version for messages that consist of
both a plain-text and html (rich-text) versions of the body-text. You change both a plain-text and html (rich-text) versions of the body-text. You can
this by setting @code{mu4e-view-prefer-html} to @t{t}. change this by setting @code{mu4e-view-prefer-html} to @t{t}.
If there is only an html-version, or if the plain-text version is too short in If there is only an html-version, or if the plain-text version is too short in
comparison with the html part@footnote{this is for the case where the comparison with the html part@footnote{this is for the case where the
@ -1225,7 +1225,8 @@ For more information, see the @command{mu-verify} manual page.
@section Actions @section Actions
You can perform custom functions (``actions'') on messages and their You can perform custom functions (``actions'') on messages and their
attachments. For a general discussion on how to define your own, see see @ref{Actions}. attachments. For a general discussion on how to define your own, see see
@ref{Actions}.
@subsection Message actions @subsection Message actions
@ -3012,7 +3013,7 @@ normal, synchronous fashion.
@section Known issues @section Known issues
Although they are not really @emph{questions}, we end this chapter with a list Although they are not really @emph{questions}, we end this chapter with a list
of known issue and/or missing features in @t{mu4e}. Thus, users won't have to of known issues and/or missing features in @t{mu4e}. Thus, users won't have to
search in vain for things that are not there (yet), and the author can use it search in vain for things that are not there (yet), and the author can use it
as a todo-list. as a todo-list.
@ -3021,11 +3022,11 @@ as a todo-list.
utf-8}; so, if you problems with encodings, be sure to have utf-8}; so, if you problems with encodings, be sure to have
@code{(set-language-environment "UTF-8")} in your @file{~/.emacs}. @code{(set-language-environment "UTF-8")} in your @file{~/.emacs}.
@item @emph{Thread handling is incomplete.} While threads are calculated and are @item @emph{Thread handling is incomplete.} While threads are calculated and are
visible in the headers buffer, you can not collapse/open them. visible in the headers buffer, you cannot collapse/open them.
@item @emph{The key-bindings are @emph{somewhat} hard-coded.} That is, the main @item @emph{The key-bindings are @emph{somewhat} hard-coded.} That is, the main
menu assumes the default key-bindings, as do the clicks-on-bookmarks. menu assumes the default key-bindings, as do the clicks-on-bookmarks.
@item @emph{The @t{emacs} front-end of the @t{notmuch} e-mail indexer @item @emph{The @t{emacs} front-end of the @t{notmuch} e-mail indexer
@t{notmuch} conflicts with @t{mu4e}}. @t{notmuch} running in parallel with conflicts with @t{mu4e}}. @t{notmuch} running in parallel with
@t{mu4e} leads to @t{mu4e} leads to
@verbatim @verbatim
error in process filter: mu4e-error-handler: Error 70: cannot read error in process filter: mu4e-error-handler: Error 70: cannot read
@ -3036,6 +3037,9 @@ changing the name of the original message file while @t{mu4e} is working in on
it. To prevent this, deactivate @t{notmuch} in your Emacs setup. it. To prevent this, deactivate @t{notmuch} in your Emacs setup.
@end itemize @end itemize
For a more complete list, please refer to the issues-list in the
github-repository.
@node Tips and Tricks @node Tips and Tricks
@appendix Tips and Tricks @appendix Tips and Tricks
@ -3206,7 +3210,8 @@ If you have multiple accounts, you can accommodate them as well:
((string-match "Account1" maildir) ((string-match "Account1" maildir)
(setq folder (or (catch 'found (setq folder (or (catch 'found
(dolist (mailing-list my-mu4e-mailing-lists) (dolist (mailing-list my-mu4e-mailing-lists)
(if (mu4e-message-contact-field-matches msg :to (car mailing-list)) (if (mu4e-message-contact-field-matches
msg :to (car mailing-list))
(throw 'found (cdr mailing-list))))) (throw 'found (cdr mailing-list)))))
"/Account1/General"))) "/Account1/General")))
((string-match "Gmail" maildir) ((string-match "Gmail" maildir)
@ -3214,7 +3219,8 @@ If you have multiple accounts, you can accommodate them as well:
((string-match "Account2" maildir) ((string-match "Account2" maildir)
(setq folder (or (cdar (member* subject my-mu4e-subject-alist (setq folder (or (cdar (member* subject my-mu4e-subject-alist
:test #'(lambda (x y) :test #'(lambda (x y)
(string-match (car y) x)))) (string-match
(car y) x))))
"/Account2/General")))) "/Account2/General"))))
folder)) folder))
@end lisp @end lisp
@ -3227,10 +3233,12 @@ message based on the mailing list to which it was sent. This requires
another variable: another variable:
@lisp @lisp
(defvar my-mu4e-mailing-lists '(("mu-discuss@@googlegroups.com" . "/Account1/mu4e") (defvar my-mu4e-mailing-lists
("pandoc-discuss@@googlegroups.com" . "/Account1/Pandoc") '(("mu-discuss@@googlegroups.com" . "/Account1/mu4e")
("auctex@@gnu.org" . "/Account1/AUCTeX")) ("pandoc-discuss@@googlegroups.com" . "/Account1/Pandoc")
"List of mailing list addresses and folders where their messages are saved.") ("auctex@@gnu.org" . "/Account1/AUCTeX"))
"List of mailing list addresses and folders where
their messages are saved.")
@end lisp @end lisp
@node Saving outgoing messages @node Saving outgoing messages