unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Unexpected fill-paragraph behaviour in message-mode
Date: Mon, 13 Feb 2023 17:21:44 +0200	[thread overview]
Message-ID: <834jrpfv5j.fsf@gnu.org> (raw)
In-Reply-To: <20230213144113.igujfoal7ervxifu@asteria.rak.ac> (message from Ryan Kavanagh on Mon, 13 Feb 2023 09:41:13 -0500)

> Date: Mon, 13 Feb 2023 09:41:13 -0500
> From: Ryan Kavanagh <rak@rak.ac>
> 
> On Mon, Feb 13, 2023 at 03:35:08PM +0200, Eli Zaretskii wrote:
> > This problem doesn't happen if the buffer has the expected separator
> > line saying "--text follows this line--".  Why are you trying to use
> > message-mode in a buffer that is not formatted as an email message?
> 
> The line was missing because I use (neo)mutt as my email client and I
> decided to try setting my editor to "emacsclient -c", but mutt does not
> insert said separator. Is there an alternate mode I should be using when
> compose emails with non-emacs MUAs?

Yes, use Emacs as $EDITOR (assuming those MUAs support that).

Alternatively, use text-mode instead of message-mode.

> > Without that separator, message-mode doesn't know where the headers
> > end and the message body begins.
> 
> Quickly skimming message.el, it looks like message-mode (only?) supports
> mail and news. In those cases, RFC 5322 §2.1 [0] and RFC 5536 §2 [1]
> give the following separator:
> 
>     The body is simply a sequence of characters that follows the header
>     section and is separated from the header section by an empty line
>     (i.e., a line with nothing preceding the CRLF).

Wrong place to look for the relevant stuff: those RFCs describes how
email messages look _in_transit_, i.e. when they are sent over the
wire.  Here we are talking about the message in the edit buffer.
Emacs removes the separator line before sending the message (actually,
it sends the parts above and below the separator separately), so we
are in full compliance with those RFCs.

> It would be nice to be able to use emacs as an editor with non-emacs
> MUAs, so I wonder if I shouldn't file a bug report asking message.el to
> fallback on the RFC (and set mail-header-separator to "") in the cases
> where "--text follows this line--" is missing.

You could try that, but my response will be that message-mode is not
meant for this job.  It is a mode for composing email that is intended
to be sent by Emacs MUA, not for editing arbitrary text.



  parent reply	other threads:[~2023-02-13 15:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  1:11 Unexpected fill-paragraph behaviour in message-mode Ryan Kavanagh
2023-02-13 13:35 ` Eli Zaretskii
2023-02-13 14:41   ` Ryan Kavanagh
2023-02-13 15:20     ` Teemu Likonen
2023-02-13 15:21     ` Eli Zaretskii [this message]
2023-02-14 12:54       ` Ryan Kavanagh
2023-02-14 13:24         ` Jean Louis
2023-02-15  2:21           ` Emanuel Berg
2023-02-15 17:06           ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-02-13 19:07     ` Jean Louis
2023-02-15 17:02 ` Stefan Monnier via Users list for the GNU Emacs text editor

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=834jrpfv5j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).