From: "Sebastian Spaeth" <Sebastian@SSpaeth.de>
To: Jameson Rollins <jrollins@finestructure.net>,
Michal Sojka <sojkam1@fel.cvut.cz>,
James Vasile <james@hackervisions.org>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] Change From and Bcc when creating reply draft buffer
Date: Fri, 12 Mar 2010 17:00:29 +0100 [thread overview]
Message-ID: <87ljdxpm1u.fsf@SSpaeth.de> (raw)
In-Reply-To: <87pr395zvi.fsf@servo.finestructure.net>
On Fri, 12 Mar 2010 10:22:09 -0500, Jameson Rollins <jrollins@finestructure.net> wrote:
> To me it seems the issue here is the distinction between the notmuch
> CLI, and any other reader UI that uses it. AFAICT, the CLI actually has
> no need to know what "your" email address is, so I don't see why it
> should be configured in the notmuch config. Your reader on the other
> hand does need to know, so it should be set there.
+1. Except for making the "from:~me" synonym available for searches :)
> This is related to another current pet peeve of mine which is that
> notmuch puts my email address in the Bcc: field in my response template.
> I do not want to bcc myself on my responses. Generally, I don't think
> it should be the business of the CLI to set any of the header fields in
> mail that I send out.
+1 I agree. The mailer should be putting a BCC in, if that is what the
user wants, not notmuch
Sebastian
prev parent reply other threads:[~2010-03-12 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 19:40 [PATCH] Change From and Bcc when creating reply draft buffer James Vasile
2010-03-11 13:00 ` Michal Sojka
2010-03-11 14:45 ` James Vasile
2010-03-11 16:22 ` Michal Sojka
2010-03-11 19:45 ` James Vasile
2010-03-12 7:49 ` Michal Sojka
2010-03-12 15:01 ` James Vasile
2010-03-12 15:22 ` Jameson Rollins
2010-03-12 16:00 ` Sebastian Spaeth [this message]
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=87ljdxpm1u.fsf@SSpaeth.de \
--to=sebastian@sspaeth.de \
--cc=james@hackervisions.org \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.org \
--cc=sojkam1@fel.cvut.cz \
/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).