From: Sandra Snan <sandra.snan@handgranat.org>
To: notmuch@notmuchmail.org
Subject: compose-mail vs message-mail
Date: Mon, 15 Mar 2010 00:27:28 +0100 [thread overview]
Message-ID: <4b9d7091.0d67f10a.39d0.ffffab29@mx.google.com> (raw)
I took a look at notmuch.el and it uses message-mail hard-coded at a few places. My suggestion is to instead substitute compose-mail, which will honor the variable ‘mail-user-agent’.
Then, the only problem is the function notmuch-reply, which has a call to message-mode hard-coded. I don’t know what to do about that one. Hope more knowledgable minds than mine will prevail.
Maybe message-mode is better or as good as what I’m using today—but it’s still weird to hard-code it like that, and makes it harder to switch to notmuch from other emacs mail setups.
Sandra
reply other threads:[~2010-03-14 23:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b9d7091.0d67f10a.39d0.ffffab29@mx.google.com \
--to=sandra.snan@handgranat.org \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).