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

Set mu4e-compose-format-flowed to nil by default

Browse Source 
Requested by Dirk-Jan C. Binnema <djcb@djcbsoftware.nl> not to disturb
existing users.
This commit is contained in:
Christophe Troestler
2016-05-07 13:12:11 +02:00
parent af523cd05a
commit d063889e4c
2 changed files with 16 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
mu4e/mu4e.texi
View File

@ -3841,15 +3841,23 @@ devices) and here's the RFC with all the details:
@url{http://www.ietf.org/rfc/rfc2646.txt}.
Since version 0.9.17, @t{mu4e} send emails with @t{format=flowed} by
default. The transformation of your message into the proper format is
setting
@lisp
(setq mu4e-compose-format-flowed t)
@end lisp
in your Emacs init file (@file{~/.emacs} or @file{~/.emacs.d/init.el}).
The transformation of your message into the proper format is
done at the time of sending. In order to happen properly, you should
write each paragraph of your message of as a long line (i.e. without
carriage return). If you introduce unwanted newlines in your paragraph,
use @kbd{M-q} to reformat it as a single line.
If you want to send the message with long lines but without
@t{format=flowed} (because, say, the receiver does not understand it as
it is the case for Google or Github), use @kbd{M-x use-hard-newlines} or
If you want to send the message with paragraphs on single lines but
without @t{format=flowed} (because, say, the receiver does not
understand the latter as it is the case for Google or Github), use
@kbd{M-x use-hard-newlines} (to turn @code{use-hard-newlines} off) or
uncheck the box @t{format=flowed} in the @t{Text} menu when composing a
message.