From: Teemu Likonen <tlikonen@iki.fi>
To: Ryan Kavanagh <rak@rak.ac>, help-gnu-emacs@gnu.org
Subject: Re: Unexpected fill-paragraph behaviour in message-mode
Date: Mon, 13 Feb 2023 17:20:42 +0200 [thread overview]
Message-ID: <87r0utsib9.fsf@iki.fi> (raw)
In-Reply-To: <20230213144113.igujfoal7ervxifu@asteria.rak.ac>
[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]
* 2023-02-13 09:41:13-0500, Ryan Kavanagh wrote:
> 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?
> 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.
I use rarely Mutt but for those cases I have defined a derived major
mode from message-mode. See the code below. I set mail-header-separator
variable locally to empty string, and it should answer your basic
question.
(add-to-list 'auto-mode-alist '("/var/tmp/mutt-.*" . mutt-message-mode))
(defvar mutt-message-mode-map
(let ((map (make-sparse-keymap)))
map))
(define-derived-mode mutt-message-mode message-mode "Mutt"
"Major mode for editing mail."
(set-keymap-parent mutt-message-mode-map nil)
(abbrev-mode 0)
(mml-mode 0)
(setq-local mail-header-separator ""))
--
/// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/
// OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2023-02-13 15:20 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 [this message]
2023-02-13 15:21 ` Eli Zaretskii
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=87r0utsib9.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=help-gnu-emacs@gnu.org \
--cc=rak@rak.ac \
/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).