From: Leo <git@relevant-information.com>
To: notmuch@notmuchmail.org
Cc: Leo Okawa Ericson <git@relevant-information.com>
Subject: [PATCH 1/1] emacs: Make notmuch-show-next-thread return nil on failure
Date: Thu, 28 Apr 2022 12:12:19 +0200 [thread overview]
Message-ID: <20220428101217.23844-2-git@relevant-information.com> (raw)
In-Reply-To: <20220428101217.23844-1-git@relevant-information.com>
From: Leo Okawa Ericson <git@relevant-information.com>
Having notmuch-show-next-thread return non-nil on success and nil on
failure makes it easier for users to interact with notmuch via elisp.
---
emacs/notmuch.el | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/emacs/notmuch.el b/emacs/notmuch.el
index c9cf80dc..a6198f4e 100644
--- a/emacs/notmuch.el
+++ b/emacs/notmuch.el
@@ -525,14 +525,15 @@ (defun notmuch-search-show-thread (&optional elide-toggle)
(let ((thread-id (notmuch-search-find-thread-id)))
(if thread-id
(notmuch-show thread-id
- elide-toggle
- (current-buffer)
- notmuch-search-query-string
- ;; Name the buffer based on the subject.
- (format "*%s*" (truncate-string-to-width
- (notmuch-search-find-subject)
- 30 nil nil t)))
- (message "End of search results."))))
+ elide-toggle
+ (current-buffer)
+ notmuch-search-query-string
+ ;; Name the buffer based on the subject.
+ (format "*%s*" (truncate-string-to-width
+ (notmuch-search-find-subject)
+ 30 nil nil t)))
+ (message "End of search results.")
+ nil)))
(defun notmuch-tree-from-search-current-query ()
"Tree view of current query."
--
2.36.0
next prev parent reply other threads:[~2022-04-28 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 10:12 [PATCH 0/1] emacs: Make notmuch-show-next-thread return nil on failure Leo
2022-04-28 10:12 ` Leo [this message]
2022-04-29 13:59 ` [PATCH 1/1] " Tomi Ollila
2022-04-29 16:39 ` Leo Okawa Ericson
2022-04-30 16:18 ` David Bremner
2022-04-30 16:41 ` David Bremner
2022-05-02 16:50 ` Leo Okawa Ericson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220428101217.23844-2-git@relevant-information.com \
--to=git@relevant-information.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).