Now that I'm able to start using notmuch with my actual mail, I thought
I might provide some impressions from the perspective of a Gnus user.
Here's what a recent bit of the notmuch list looks like in my notmuch
buffer:
May 03 [7/7] (null) [PATCH] Customize saved search
Does notmuch-search-result-format allow multiple-line formats? i.e.:
[5/5] [notmuch] an other ready-to-use store option for notmuch : CouchDB
Paul R., Jed Brown, martin f. krafft, James Westby (f//notmuch unread)
[2/2] [notmuch] [PATCH] Do not segfault on empty mime parts
martin
Now that I'm able to start using notmuch with my actual mail, I thought
I might provide some impressions from the perspective of a Gnus user.
Here's what a recent bit of the notmuch list looks like in my notmuch
buffer:
May 03 [7/7] (null) [PATCH] Customize saved search
Does notmuch-search-result-format allow multiple-line formats? i.e.:
[5/5] [notmuch] an other ready-to-use store option for notmuch : CouchDB
Paul R., Jed Brown, martin f. krafft, James Westby (f//notmuch unread)
[2/2] [notmuch] [PATCH] Do not segfault on empty mime parts
martin
I've started to look at the elisp, and wondered why
notmuch-search-result-format expected strings rather than symbols for
the field names, i.e.:
(("date" . "%s ")
("count" . "%-7s ")
("authors" . "%-20s ")
("subject" . "%s ")
("tags" . "(%s)"))
instead of
