From: Felipe Contreras <felipe.contreras@gmail.com>
To: Sebastian Spaeth <Sebastian@sspaeth.de>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH 0/3] composing patches
Date: Fri, 10 Dec 2010 17:35:17 +0200 [thread overview]
Message-ID: <AANLkTimq7On+1tnpaCXhnd8H=M+5AH6Ss6k1fDL296V-@mail.gmail.com> (raw)
In-Reply-To: <877hfi1ql7.fsf@SSpaeth.de>
On Fri, Dec 10, 2010 at 1:20 AM, Sebastian Spaeth <Sebastian@sspaeth.de> wrote:
> On Fri, 10 Dec 2010 00:32:49 +0200, Felipe Contreras <felipe.contreras@gmail.com> wrote:
>> I don't know how it works in gnus, but at least on the vim mode, the output
>> generated by 'notmuch reply' is not ready to be sent, at least the Message-ID
>> field is needed, and also is nice to have the User-Agent.
>
> But notmuch is not the User-Agent. That's why the emacs UI fills in the
> User-Agent value itself. I am not sure on the policy of creating
> Message-IDs, perhaps notmuch-reply could actually fill in some defaults there.
Why it's not? The emacs UI is not really doing anything on top of
'notmuch reply'. And if it is, it can very well override that value.
Besides, what about other users (vim)? Why not make the output of
'notmuch reply' ready to be dumped to sendmail?
It seems right now there's a lot of reliance on emacs UI, and gnus.
--
Felipe Contreras
next prev parent reply other threads:[~2010-12-10 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 22:32 [PATCH 0/3] composing patches Felipe Contreras
2010-12-09 22:32 ` [PATCH 1/3] reply: add message-id header Felipe Contreras
2010-12-09 22:32 ` [PATCH 2/3] reply: add user-agent field Felipe Contreras
2010-12-09 22:32 ` =?no?q?=5BPATCH=203/3=5D=20Add=20=27compose=27=20command?= Felipe Contreras
2010-12-09 23:20 ` [PATCH 0/3] composing patches Sebastian Spaeth
2010-12-10 15:35 ` Felipe Contreras [this message]
2010-12-10 16:04 ` Jameson Rollins
2010-12-10 16:38 ` Sebastian Spaeth
2010-12-10 23:53 ` Michal Sojka
2011-05-04 20:30 ` Felipe Contreras
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='AANLkTimq7On+1tnpaCXhnd8H=M+5AH6Ss6k1fDL296V-@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=Sebastian@sspaeth.de \
--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).