unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: Alex Ghitza <aghitza@gmail.com>, Jed Brown <jed@59A2.org>,
	notmuch@notmuchmail.org
Subject: Re: keeping a copy of sent mail locally
Date: Sat, 19 Dec 2009 18:37:12 -0800	[thread overview]
Message-ID: <87aaxextev.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <54hbrmze3v.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]

On Sun, 20 Dec 2009 11:24:52 +1100, Alex Ghitza <aghitza@gmail.com> wrote:
> However, if I'm using notmuch in emacs and press 'm' to compose a new
> message, then the Bcc header is not added automatically and I guess it's
> not surprising that the rest doesn't work as expected.

Yeah, sorry about that. That's a known bug.

> So where is the difference between 'm' and 'r' coming from?

The difference is that 'r' actually runs the "notmuch reply" command and
that command explicitly puts your own address into the Bcc. So this is
happening outside of any emacs code.

When you hit 'm', though, there's not any notmuch code involved,
(neither C code, nor emacs lisp), as it's currently just running
`message-mail'. So we need to figure out how to configure (or hook) that
to insert the Bcc, and then we can fix notmuch.el to do this without any
user configuration.

> I have (setq mail-self-blind t)  in my .emacs, and I thought that should take
> care of things, but it obviously doesn't.

Ah, interesting.

I'm guessing that that variable would apply to the "mail" mode stuff in
emacs, but perhaps not the "message" mode stuff we're using.

Yes, emacs mail support is a huge pile of very similar, but incompatible
systems.

Hopefully someone can fix this soon, since I really don't like the fact
that I'm currently not getting copies of several messages that I'm
composing and sending.

-Carl

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2009-12-20  2:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19  4:41 keeping a copy of sent mail locally Alex Ghitza
2009-12-19 10:55 ` Jed Brown
2009-12-20  0:24   ` Alex Ghitza
2009-12-20  2:37     ` Carl Worth [this message]
2009-12-20  2:50       ` Keith Packard
2009-12-20  4:29         ` Alex Ghitza
2009-12-20  5:02           ` Keith Packard
2009-12-20 18:22             ` Marten Veldthuis
2009-12-20 18:31               ` Jameson Graef Rollins
2009-12-20 18:51                 ` Adam Sjøgren
2009-12-21 10:08                   ` Alex Ghitza
2009-12-21 10:19                     ` Marten Veldthuis
2009-12-21  9:57                 ` Alex Ghitza
2009-12-21 14:46                   ` Jameson Graef Rollins
2009-12-21 17:27           ` Carl Worth
2009-12-21 19:39             ` Adrien BUSTANY
2009-12-21 20:24               ` Carl Worth

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=87aaxextev.fsf@yoom.home.cworth.org \
    --to=cworth@cworth.org \
    --cc=aghitza@gmail.com \
    --cc=jed@59A2.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).