Re: Message Id in search summary

2019-06-03 Thread David Bremner
meOme writes: > Is it possible to get the mail-id in the summary (instead of, or additional > to) the thread-id? > What's the way to go? > Thanks a lot! Currently the summary output is not configurable. It would be nice to have some kind of "format string" or equivalent, but so far nobody

Re: Message Id in search summary

2019-06-03 Thread Rollins, Jameson
On Mon, Jun 03 2019, meOme wrote: > I use > notmuch search myWord > for the search and the output seems to be the same as > notmuch search --output=summary myWord > So output=summary is the default, right? > Now (on a user's klick) I would like to show the Message from the saerch > result. > The

Message Id in search summary

2019-06-03 Thread meOme
Hi, I use notmuch search myWord for the search and the output seems to be the same as notmuch search --output=summary myWord So output=summary is the default, right? Now (on a user's klick) I would like to show the Message from the saerch result. The Problem is, that there's only the Thread-Id in

Re: [FEATURE] indexing arbitrary headers

2019-06-03 Thread Łukasz Stelmach
It was <2019-05-30 czw 22:27>, when Daniel Kahn Gillmor wrote: > On Sat 2017-06-03 13:28:46 -0300, David Bremner wrote: >> Łukasz Stelmach writes: >> >>> I'd like to ask for a new feature: indexing of arbitrary headers. Not >>> all headers but a few selected by users. [...] > I just wanted to

Re: feature request: caching message arrival time

2019-06-03 Thread Örjan Ekeberg
Daniel Kahn Gillmor writes: > Sure, assuming that you trust the closest MTA in the chain of MTAs that > handed the message off to you, since an adversarial proximal MTA could > manipulate all the existing Received: headers as well. > > But I'm a bit uncomfortable with it: this sort of protection

Re: notmuch-message-mark-replied

2019-06-03 Thread Rollins, Jameson
On Mon, Jun 03 2019, Örjan Ekeberg wrote: > "Rollins, Jameson" writes: >> I have the following in my emacs config: >> >> '(message-send-hook >>(quote >> (notmuch-message-mark-replied notmuch-fcc-header-setup))) >> >> I'm wondering what if anything I should replace this with. > > You

Re: notmuch-message-mark-replied

2019-06-03 Thread Örjan Ekeberg
"Rollins, Jameson" writes: > I have the following in my emacs config: > > '(message-send-hook >(quote > (notmuch-message-mark-replied notmuch-fcc-header-setup))) > > I'm wondering what if anything I should replace this with. You should probably remove this altogether.

Re: notmuch-message-mark-replied

2019-06-03 Thread David Bremner
"Rollins, Jameson" writes: > I have the following in my emacs config: > > '(message-send-hook >(quote > (notmuch-message-mark-replied notmuch-fcc-header-setup))) As far as I know it can be deleted. At least both marking as replied and fcc headers work OK for me without it. d

Re: notmuch-message-mark-replied

2019-06-03 Thread Rollins, Jameson
On Mon, Jun 03 2019, David Bremner wrote: > Örjan Ekeberg writes: > >> David Bremner writes: >>> In d9800c8 we deleted the function notmuch-message-mark-replied. >>> >>> Should we make a deprecated-alias for >>> notmuch-message-apply-queued-tag-changes? >> >> The two functions are not

Re: feature request: caching message arrival time

2019-06-03 Thread Ralph Seichter
* Daniel Kahn Gillmor: > Since notmuch actually knows when it recieved the message [...] Not meaning to complicate things, but Notmuch does not receive messages at all. ;-) One needs to rely on some software to populate the Maildir tree (Dovecot LMTP in my case, Postfix or some other MTA for

Re: feature request: caching message arrival time

2019-06-03 Thread Daniel Kahn Gillmor
On Mon 2019-06-03 10:57:15 +0200, Örjan Ekeberg wrote: > Daniel Kahn Gillmor writes: > >> So Autocrypt defines the "effective date" of a message as the *earliest* >> of two dates: the date that the message is first seen, and the Date: >> header itself. So we want our augmented Autocrypt header

Re: Release 0.29.

2019-06-03 Thread David Bremner
David Bremner writes: > I know there are several things "in progress", but we've also > accumulated a fair amount of change since 0.28. I am planning a feature > freeze for 0.29 on May 31 and (hopefully) a release on June 7. > > d 0.29_rc1 tagged, uploaded to Debian Experimental. All going

Re: [PATCH] doc: use separate doctrees for distinct builders

2019-06-03 Thread David Bremner
David Bremner writes: > It seems our previous attempt with order-only targets was not > sufficient to avoid problems with sphinx-builds doctree cache [0]. > Looking around at other people's approaches [1], using seperate > doctrees was suggested. I guess there might be a slight loss of >

Re: notmuch-message-mark-replied

2019-06-03 Thread David Bremner
Örjan Ekeberg writes: > David Bremner writes: >> In d9800c8 we deleted the function notmuch-message-mark-replied. >> >> Should we make a deprecated-alias for >> notmuch-message-apply-queued-tag-changes? > > The two functions are not interchangeable, so it may not be appropriate > to mark it as

Re: notmuch-message-mark-replied

2019-06-03 Thread Örjan Ekeberg
David Bremner writes: > In d9800c8 we deleted the function notmuch-message-mark-replied. > > Should we make a deprecated-alias for > notmuch-message-apply-queued-tag-changes? The two functions are not interchangeable, so it may not be appropriate to mark it as an alias.

Re: feature request: caching message arrival time

2019-06-03 Thread Örjan Ekeberg
Daniel Kahn Gillmor writes: > So Autocrypt defines the "effective date" of a message as the *earliest* > of two dates: the date that the message is first seen, and the Date: > header itself. So we want our augmented Autocrypt header ingestion > routine to search for all other messages we know