unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Radu Butoi <rbutoi@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Sending mail: line wrapping and quoted-printable encoding
Date: Sat, 25 Apr 2020 20:19:15 -0400	[thread overview]
Message-ID: <prg8eesbnloc.fsf@butoi.nyc.corp.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

Hello all,

I've recently set up my mail in Emacs, and it works well. Gmail, though,
doesn't support [1] format=flowed, resulting in the hard-to-read comb
effect when viewing on mobile, which I'd like to avoid. Doing some more
research, I see that the quoted-printable encoding (which Gmail does
support [2], and I've confirmed) can also be used to avoid hard line
breaks while keeping under the line length limit.

Now, I'd like to configure Emacs to send mail using this encoding. To
test this I overwrite `sendmail-program` to log what Emacs sends.
Reading the message-mode and Emacs MIME manuals, I tried setting the
following variables:

(setq
 mm-content-transfer-encoding-defaults
 '((".*" quoted-printable))
 mm-body-charset-encoding-alist
 '((iso-8859-1 . quoted-printable)
   (utf-8      . quoted-printable))
 mm-use-ultra-safe-encoding t)

When sending, no encoding to quoted-printable is done (and there's no
Content-Transfer-Encoding header). To try to debug this further,
inserted the following into a buffer and ran M-: (mml-to-mime)


[-- Attachment #2: Type: text/plain, Size: 46 bytes --]

test test test <...longer than 78 columns...>

[-- Attachment #3: Type: text/plain, Size: 612 bytes --]


And there is still no encoding header or wrapping with =. Does anyone
know what is going on here?

More generally, since I'm new to terminal-based email, what is the
etiquette around hard-wrapping (or not)? Would it be rude to send
paragraphs as one logical line (wrapped-in-transmission by
quoted-printable) and expect people to soft-wrap?

Thanks in advance,
Radu

[1]: https://useplaintext.email/, and many blog posts mentioning the
same. It seems like Gmail used to support this, from the screenshot in
https://github.com/legoscia/messages-are-flowing.

[2]: https://mathiasbynens.be/notes/gmail-plain-text

             reply	other threads:[~2020-04-26  0:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26  0:19 Radu Butoi [this message]
2020-04-26  0:24 ` Sending mail: line wrapping and quoted-printable encoding Radu Butoi
2020-04-26  0:38   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-26 18:44     ` Radu Butoi
2020-04-27  7:50       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-26  8:00 ` Gregor Zattler
2020-04-26 18:44   ` Radu Butoi
2020-04-27  8:52     ` Gregor Zattler
2020-04-27 22:20       ` Radu Butoi
2020-04-28 14:37         ` Gregor Zattler
2020-05-05 21:44           ` Radu Butoi
2020-05-06  7:37             ` Gregor Zattler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=prg8eesbnloc.fsf@butoi.nyc.corp.google.com \
    --to=rbutoi@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).