Re: emacs: Use of seq-some breaks 'nil' values in notmuch-fcc-dirs
David Bremner writes:
> Toke Høiland-Jørgensen writes:
>
>> Hi
>>
>> Commit 16b2db0986ce ("emacs: various cosmetic improvements") switched
>> over notmuch-fcc-header-setup to use 'seq-some' to parse the
>> notmuch-fcc-dirs variables. However, this seems to have broken the use
>> of 'nil' values in the list. Specifically, I have notmuch-fcc-dirs set
>> to something like:
>>
>> '(("toke@onemail.alias" . "alias1/Sent +sent -unread")
>> ("toke@another.alias" . nil)
>> (".*" . "Sent +sent -unread"))
>>
>> and since that update, I end up with "Sent +sent -unread" as the FCC
>> value for emails I initiate from toke@another.alias.
>>
>> Any chance this could be fixed?
>
> This should be fixed in commit b03b0d4e
Indeed it is - thanks! :)
-Toke
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: emacs: Use of seq-some breaks 'nil' values in notmuch-fcc-dirs
Toke Høiland-Jørgensen writes:
> Hi
>
> Commit 16b2db0986ce ("emacs: various cosmetic improvements") switched
> over notmuch-fcc-header-setup to use 'seq-some' to parse the
> notmuch-fcc-dirs variables. However, this seems to have broken the use
> of 'nil' values in the list. Specifically, I have notmuch-fcc-dirs set
> to something like:
>
> '(("toke@onemail.alias" . "alias1/Sent +sent -unread")
> ("toke@another.alias" . nil)
> (".*" . "Sent +sent -unread"))
>
> and since that update, I end up with "Sent +sent -unread" as the FCC
> value for emails I initiate from toke@another.alias.
>
> Any chance this could be fixed?
This should be fixed in commit b03b0d4e
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: emacs: Use of seq-some breaks 'nil' values in notmuch-fcc-dirs
Toke Høiland-Jørgensen writes:
> Commit 16b2db0986ce ("emacs: various cosmetic improvements") switched
> over notmuch-fcc-header-setup to use 'seq-some' to parse the
> notmuch-fcc-dirs variables. However, this seems to have broken the use
> of 'nil' values in the list. Specifically, I have notmuch-fcc-dirs set
> to something like:
>
> '(("toke@onemail.alias" . "alias1/Sent +sent -unread")
> ("toke@another.alias" . nil)
> (".*" . "Sent +sent -unread"))
>
> and since that update, I end up with "Sent +sent -unread" as the FCC
> value for emails I initiate from toke@another.alias.
On the one hand that behaviour was undocumented. On the other hand, it
does seem like a useful thing to want to do. Hopefully Jonas can more
quickly untangle what happened there than I can.
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
emacs: Use of seq-some breaks 'nil' values in notmuch-fcc-dirs
Hi
Commit 16b2db0986ce ("emacs: various cosmetic improvements") switched
over notmuch-fcc-header-setup to use 'seq-some' to parse the
notmuch-fcc-dirs variables. However, this seems to have broken the use
of 'nil' values in the list. Specifically, I have notmuch-fcc-dirs set
to something like:
'(("toke@onemail.alias" . "alias1/Sent +sent -unread")
("toke@another.alias" . nil)
(".*" . "Sent +sent -unread"))
and since that update, I end up with "Sent +sent -unread" as the FCC
value for emails I initiate from toke@another.alias.
Any chance this could be fixed?
Thanks,
-Toke
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
