alx/mu4e
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mu4e: Minor fixes to texinfo documentation

Browse Source
This commit is contained in:
Christophe Troestler
2021-04-26 01:40:11 +02:00
parent 3799975714
commit a9a874937e
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
mu4e/mu4e.texi
View File

@ -143,7 +143,7 @@ like @t{notmuch}@footnote{@url{https://notmuchmail.org/}} and
@t{sup}@footnote{@url{https://sup-heliotrope.github.io/}}. @t{sup}@footnote{@url{https://sup-heliotrope.github.io/}}.
However, @t{mu4e}'s user-interface is quite different. @t{mu4e}'s mail However, @t{mu4e}'s user-interface is quite different. @t{mu4e}'s mail
handling (deleting, moving etc.) is inspired by handling (deleting, moving, etc.)@: is inspired by
Wanderlust@footnote{@url{http://www.gohome.org/wl/}} (another Wanderlust@footnote{@url{http://www.gohome.org/wl/}} (another
Emacs-based e-mail client), Emacs-based e-mail client),
@t{mutt}@footnote{@url{http://www.mutt.org/}} and the @t{dired} @t{mutt}@footnote{@url{http://www.mutt.org/}} and the @t{dired}
@ -1091,8 +1091,8 @@ search results.
@node HV Custom headers @node HV Custom headers
@section Custom headers @section Custom headers
Sometimes the normal headers that @t{mu4e} offers (Date, From, To, Subject Sometimes the normal headers that @t{mu4e} offers (Date, From, To, Subject,
etc.) may not be enough. For these cases, @t{mu4e} offers @emph{custom etc.)@: may not be enough. For these cases, @t{mu4e} offers @emph{custom
headers} in both the headers-view and the message-view. headers} in both the headers-view and the message-view.
You can do so by adding a description of your custom header to You can do so by adding a description of your custom header to
@ -1346,7 +1346,7 @@ your configuration (and see the docstring for
(add-to-list 'mm-discouraged-alternatives "text/richtext")) (add-to-list 'mm-discouraged-alternatives "text/richtext"))
@end lisp @end lisp
When displaying rich-text messages inline, @t{mu4e} (through @t{gnus})x When displaying rich-text messages inline, @t{mu4e} (through @t{gnus})
uses the @t{shr} built-in HTML-renderer. If you're using a dark color uses the @t{shr} built-in HTML-renderer. If you're using a dark color
theme, and the messages are hard to read, it can help to change the theme, and the messages are hard to read, it can help to change the
luminosity, e.g.: luminosity, e.g.:
@ -1387,7 +1387,7 @@ images in Github notifications, do the following:
@node MSGV Custom headers @node MSGV Custom headers
@section Custom headers @section Custom headers
Sometimes the normal headers (Date, From, To, Subject etc.) may not be Sometimes the normal headers (Date, From, To, Subject, etc.)@: may not be
enough. For these cases, @t{mu4e} offers @emph{custom headers} in both enough. For these cases, @t{mu4e} offers @emph{custom headers} in both
the headers-view and the message-view. the headers-view and the message-view.
@ -1844,8 +1844,8 @@ For more information, see the @command{mu-verify} manual page.
@node OMSGV Custom headers @node OMSGV Custom headers
@section Custom headers @section Custom headers
Sometimes the normal headers that @t{mu4e} offers (Date, From, To, Subject Sometimes the normal headers that @t{mu4e} offers (Date, From, To, Subject,
etc.) may not be enough. For these cases, @t{mu4e} offers @emph{custom etc.)@: may not be enough. For these cases, @t{mu4e} offers @emph{custom
headers} in both the headers-view and the message-view. headers} in both the headers-view and the message-view.
See @ref{HV Custom headers} for an example of this; the difference for the See @ref{HV Custom headers} for an example of this; the difference for the
@ -4177,7 +4177,7 @@ Next step: let's make a @t{mu4e} configuration for this:
@end lisp @end lisp
And that's it --- put the above in your @file{~/.emacs}, change @t{USERNAME} And that's it --- put the above in your @file{~/.emacs}, change @t{USERNAME}
etc. to your own, and restart Emacs, and run @kbd{M-x mu4e}. etc.@: to your own, and restart Emacs, and run @kbd{M-x mu4e}.
@node CONF Other settings @node CONF Other settings
@section Other settings @section Other settings