Re: Sending mail succeeded but signaled failure

Dan Čermák writes: > Justus Winter writes: > >> David Bremner writes: >> >>> Justus Winter writes: >>> Hello, I just embarrassed myself a little by sending the same mail over and over again. The reason for that is that notmuch-emacs signaled failure, i.e. it

lastmod based on date/time

Would it be possible to search for lastmod messages based on time rather than revision ID? Using revision ID is convenient for tools/scripts, but not for actual everyday use. I sometimes find myself needing to find a message that I accidentally archived/moved and it would be convenient if I

Re: Sending mail succeeded but signaled failure

Justus Winter writes: > David Bremner writes: > >> Justus Winter writes: >> >>> Hello, >>> >>> I just embarrassed myself a little by sending the same mail over and >>> over again. The reason for that is that notmuch-emacs signaled failure, >>> i.e. it displayed an error message in the status

[PATCH 1/2] test/emacs: add known broken test for inlining on refresh.

This duplicates the bug reported by Al [1] [1]: id:877d41nmr1@gmail.com --- test/T450-emacs-show.sh | 22 ++ 1 file changed, 22 insertions(+) diff --git a/test/T450-emacs-show.sh b/test/T450-emacs-show.sh index 37940c96..b77f8c0e 100755 --- a/test/T450-emacs-show.sh +++

[PATCH 2/2] emacs/show: restrict inlined mimetypes on refresh.

This fixes the bug reported by Al [1]. Essentially apply the same fix as [2] in a different place. [1]: id:877d41nmr1@gmail.com [2]: 90a7c1af368a527700dcde9b0dcbd760afc7bd92 --- emacs/notmuch-show.el | 1 + test/T450-emacs-show.sh | 1 - 2 files changed, 1 insertion(+), 1 deletion(-) diff

Re: lastmod based on date/time

Al Haji-Ali writes: > Would it be possible to search for lastmod messages based on time > rather than revision ID? Using revision ID is convenient for > tools/scripts, but not for actual everyday use. > The modification time is not saved in the database. > I sometimes find myself needing to

[PATCH] NEWS: initial set of NEWS for 0.37.

There are one or two more changes to apply (and potentially document) before release, but this covers most of my commits. --- NEWS | 35 +++ 1 file changed, 35 insertions(+) diff --git a/NEWS b/NEWS index 44551b82..1e0b6a6c 100644 --- a/NEWS +++ b/NEWS @@ -1,12