Rather than returning the result of kill-buffer,
with-current-notmuch-show-message should return the result of calling
the passed body.
---
emacs/notmuch-show.el | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index
I started looking at how to add autocrypt support based on
https://git.sr.ht/~zge/autocrypt.
Sending seems straightforward, as far as I understand autocrypt, at
least.
Dealing with inbound messages requires a few framework changes in
the existing notmuch emacs code, which is these two patches.
Add a hook called after inserting each message into the buffer showing
messages.
---
emacs/notmuch-show.el | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index 761be252..cda0bfe0 100644
--- a/emacs/notmuch-show.el
+++
As well as allowing headers to be specified in the various result
format lists, allow functions that can be used to implement per-user
logic when generating the results.
v3:
- Push the function test into the pcase (bremner).
- Rebase to master (bremner).
David Edmondson (3):
emacs: Use pcase
If the car of an element in notmuch-search-result-format is a
function, insert the result of calling the function into the buffer.
This allows a user to generate custom fields in the output of a search
result. For example, with:
(defun -notmuch-result-flags (format-string result)
(let
Rather than lots of string-equal calls, use the pcase macro.
---
emacs/notmuch.el | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/emacs/notmuch.el b/emacs/notmuch.el
index 6d37c623..b9cee19c 100644
--- a/emacs/notmuch.el
+++
If the car of an element in notmuch-tree-result-format or
notmuch-unthreaded-result-format is a function, insert the result of
calling the function into the buffer.
---
emacs/notmuch-tree.el | 3 +++
1 file changed, 3 insertions(+)
diff --git a/emacs/notmuch-tree.el b/emacs/notmuch-tree.el
index
Hi Olly, David, xapian and notmuch developers,
* Olly Betts [12. Feb. 2021]:
> On Thu, Feb 11, 2021 at 06:53:27AM -0400, David Bremner wrote:
>> At this point I don't really have any good ideas, so I'm waiting for
>> results from the 1.4.18 trial.
>
> I've uploaded a backport, but it's the first
I did not look at logs, but I have had problem in other scenarios. The
way I debugged was to use strace to get a list of all files the tests
accessed. From that list I could recognize that some files that should
have been in separate temp directories were not thread-specific and
solution was to