On Thu, 03 Jun 2010 17:02:10 -0700, Carl Worth <cworth@cworth.org> wrote: > On Wed, 28 Apr 2010 17:33:18 -0400, Jameson Rollins <jrollins@finestructure.net> wrote: > > Now that we finally have good built-in fcc support, we can finally get > > rid of the annoying bcc in notmuch-reply. > > I do want to apply this patch. But before I do I want the emacs > interface to be doing *something* to ensure the user gets a copy of all > sent messages by default. I've now got that all setup. I fixed the emacs FCC code to treat the notmuch-fcc-dirs variable as relative to the notmuch database path[*] (rather than the former message-directory variable which required the user to do extra configuration settings). And with that, I've now turned FCC within emacs on by default, (to a directory named "sent"---feel free to customize the 'notmuch-fcc-dirs if you'd like it to go somewhere by default). So I've applied these patches now (after fixing them up against the latest code, such as the modularized test suite). > Either way, I know that some users *do* want to use Bcc (or even Cc!) > rather than Fcc. So I'd also like an emacs variable to select that > too. For people who want this, the FCC can be turned off by setting notmuch-fcc-dirs to nil. Then, to get Bcc or Cc turned on for all mails, the right answer is probably to use a message-mode hook, (or even a notmuch hook if we have the right one already). I imagine some documentation on this would be useful. So if someone is motivated to figure it out, please let us know. -Carl [*] Implementing this required allowing the emacs interface to be able to get at notmuch configuration settings. So I've added a new "notmuch config" command which can be used as follows: $ notmuch config set user.name "Carl Worth" $ notmuch config get user.name Carl Worth etc. Perhaps others might find this useful. -- carl.d.worth@intel.com