From: Jean Louis <bugs@gnu.support>
To: Ryan Kavanagh <rak@rak.ac>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Unexpected fill-paragraph behaviour in message-mode
Date: Mon, 13 Feb 2023 22:07:28 +0300 [thread overview]
Message-ID: <Y+qKcMgNwbqhQq8N@protected.localdomain> (raw)
In-Reply-To: <20230213144113.igujfoal7ervxifu@asteria.rak.ac>
* Ryan Kavanagh <rak@rak.ac> [2023-02-13 17:42]:
> Is there an alternate mode I should be using when compose emails
> with non-emacs MUAs?
I use all time best e-mail client for Emacs, also known as Mutt. I
know it is external and non-Emacs.
My setting is peculiar:
macro compose 0 ":set editor=mutt-record-email.lisp<enter><edit-headers>:set editor=emacsclient<enter>"
as I like to record e-mail externally, for statistics and other
macros, but normal setting would be:
set editor=emacsclient
> Looking at the source in message.el, it usually finds the separation
> between header and body using:
>
> (re-search-forward
> (concat "^" (regexp-quote mail-header-separator) "$")
>
> It would be nice to be able to use emacs as an editor with non-emacs
> MUAs
The above is not much relevant to your quest.
Any external MUA can use Emacs either directly by "emacs" command or
"emacsclient".
> 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 may say how I do it:
M-x mail to compose e-mails. I have more easier way to do it, I can
compose directly to all people by single click, where my identity and
recipient, including Cc, Bcc is all setup correctly. Mail is first
saved in file, and later sorted in Maildirs, e-mail is dispatched.
To read e-mails, I use Mutt
The Mutt E-Mail Client:
http://mutt.org/
and I am so much more efficient than with any Emacs client, but any
MUA can be used, including Thunderbird, it has external editor option
(or internal).
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-02-13 19:07 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
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 [this message]
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=Y+qKcMgNwbqhQq8N@protected.localdomain \
--to=bugs@gnu.support \
--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).