From: Carl Worth <cworth@cworth.org>
To: Rob Browning <rlb@defaultvalue.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH] Move notmuch-fcc-header-setup to message-header-setup-hook.
Date: Wed, 27 Oct 2010 17:40:26 -0700 [thread overview]
Message-ID: <87wrp3p2th.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <1284323018-8423-1-git-send-email-rlb@defaultvalue.org>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
On Sun, 12 Sep 2010 15:23:37 -0500, Rob Browning <rlb@defaultvalue.org> wrote:
> Here's a small patch to move notmuch-fcc-header-setup from
> message-send-hook to message-header-setup-hook. This is nice because
> it allows you to see what's going to happen and make adjustments if
> you like.
This is great. I do like the assurance of seeing the Fcc header there.
I've applied this patch now, (was only waiting for the recent work I
just completed to turn on Fcc by default and remove the Bcc from
"notmuch reply").
As mentioned before, anyone who doesn't want to see the Fcc header when
composing messages can set the message-hidden-headers variable.
It might also be nice for someone to add a notmuch-hidden-headers
variable. I think I'm inclined to allow people to customize the most
common settings within the notmuch customization, (without having to
hunt through message-mode customization as well).
-Carl
--
carl.d.worth@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2010-10-28 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 20:23 [PATCH] Move notmuch-fcc-header-setup to message-header-setup-hook Rob Browning
2010-09-12 20:23 ` Rob Browning
2010-09-14 2:43 ` Jameson Rollins
2010-09-14 18:58 ` Sebastian Spaeth
2010-09-14 19:07 ` Jameson Rollins
2010-09-14 18:06 ` keybindings Daniel Goldin
2010-09-14 18:37 ` keybindings Jameson Rollins
2010-10-28 0:40 ` Carl Worth [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=87wrp3p2th.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=notmuch@notmuchmail.org \
--cc=rlb@defaultvalue.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).