From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id D45D5431FBC; Mon, 21 Dec 2009 09:27:05 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nGmwui-3GI0e; Mon, 21 Dec 2009 09:27:05 -0800 (PST) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 313D8431FAE; Mon, 21 Dec 2009 09:27:05 -0800 (PST) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id D8146254307; Mon, 21 Dec 2009 09:27:04 -0800 (PST) From: Carl Worth To: Alex Ghitza , Keith Packard , Jed Brown , notmuch@notmuchmail.org In-Reply-To: <54eimqz2sk.fsf@gmail.com> References: <54hbrnpod1.fsf@gmail.com> <8763836xnv.fsf@59A2.org> <54hbrmze3v.fsf@gmail.com> <87aaxextev.fsf@yoom.home.cworth.org> <54eimqz2sk.fsf@gmail.com> Date: Mon, 21 Dec 2009 09:27:04 -0800 Message-ID: <871viotezb.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Subject: Re: keeping a copy of sent mail locally X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 17:27:06 -0000 --=-=-= On Sun, 20 Dec 2009 15:29:15 +1100, Alex Ghitza wrote: > It looks like we need a way to get the primary email address from the > config file. Yes, we definitely need that. > Actually, while we're at it, we can consider making this > more flexible and adding a new option to the config file (e.g. bcc=...) > which would take a semicolon-separated list of email addresses (in case > someone wants to always bcc an address other than the primary one). And that would be fine too. > Is there a nice clean way of getting the config variables in notmuch.el? > Or should this go into a new file notmuch-compose.c? Note that the > latter would imply having a new command like "notmuch compose". I think we want a new C file to make it easy to ask for options out of the configuration file. The operation of "notmuch compose" seems simple enough to not be necessary, (though maybe it would make it easier to get standard behavior among different interfaces). > It's not a big deal, but now the same thing must be set in two different > places (.notmuch-config and .emacs), Right. I definitely want to get away from that. I want people to put stuff into .notmuch-config and then have our emacs code "just work". Our emacs code could, for example, set variables like user-full-name and user-mail-address from the notmuch configuration, (it wouldn't override these if already set I think). > Sorry about writing a lot of prose and no code! I'd like to get a sense > for people's reactions before trying to write a patch for this. No problem at all. Thanks for the thoughts and ideas. -Carl --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLL6/o6JDdNq8qSWgRAi2ZAJ4xl8EwivOe2kUViqIvNDbCVPp6aACgqKdU Fzl2X1ktkK1r0YaE8m8PDF4= =F/du -----END PGP SIGNATURE----- --=-=-=--