On Thu, 04 Nov 2010 18:03:11 -0500, Rob Browning
wrote:
> If you're going to go that far, you might want to allow a function (or
> form) too (a-la gnus).
Please, feel free. I'm a bcc-kinda-guy myself.
On Thu, 04 Nov 2010 18:03:11 -0500, Rob Browning wrote:
> If you're going to go that far, you might want to allow a function (or
> form) too (a-la gnus).
Please, feel free. I'm a bcc-kinda-guy myself.
___
notmuch mailing list
notmuch@notmuchmail.org
htt
Re-work the declaration and definition of `notmuch-fcc-dirs'. The
variable now allows three types of values:
- nil: no Fcc header is added,
- a string: the value of `notmuch-fcc-dirs' is the name of the
folder to use,
- a list: the folder is chosen based on the From address of the
current me
David Edmondson writes:
> After wanting to be able to set `notmuch-fcc-dirs' to `nil' using
> custom, I got sucked in.
If you're going to go that far, you might want to allow a function (or
form) too (a-la gnus). As an example, that can be handy when you want
to file mail based on the year:
David Edmondson writes:
> After wanting to be able to set `notmuch-fcc-dirs' to `nil' using
> custom, I got sucked in.
If you're going to go that far, you might want to allow a function (or
form) too (a-la gnus). As an example, that can be handy when you want
to file mail based on the year:
Re-work the declaration and definition of `notmuch-fcc-dirs'. The
variable now allows three types of values:
- nil: no Fcc header is added,
- a string: the value of `notmuch-fcc-dirs' is the name of the
folder to use,
- a list: the folder is chosen based on the From address of the
current me
