Hello, It's quite common nowadays for Emacs users to use `setq` to set values for custom, but doing that with notmuch-search-oldest-first it gets overwritten currently in #'notmuch-search.
I'm attaching a patch that modifies the code to retain the existing value by using a conditional `and`. Cheers,
From 320eec00ff828af67bd75dc38c168cd40a18bbcc Mon Sep 17 00:00:00 2001 From: Thanos Apollo <[email protected]> Date: Thu, 15 Jan 2026 11:07:31 +0200 Subject: [PATCH] emacs: use oldest-first conditions instead of overwriting. --- emacs/notmuch.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/emacs/notmuch.el b/emacs/notmuch.el index 69aff347..bd0e061b 100644 --- a/emacs/notmuch.el +++ b/emacs/notmuch.el @@ -1098,7 +1098,7 @@ the configured default sort order." ;; Don't track undo information for this buffer (setq buffer-undo-list t) (setq notmuch-search-query-string query) - (setq notmuch-search-oldest-first oldest-first) + (setq notmuch-search-oldest-first (and notmuch-search-oldest-first oldest-first)) (setq notmuch-search-target-thread target-thread) (setq notmuch-search-target-line target-line) (setq notmuch-search-hide-excluded hide-excluded) -- 2.52.0
-- Thanos Apollo ☧ https://thanosapollo.org
signature.asc
Description: PGP signature
_______________________________________________ notmuch mailing list -- [email protected] To unsubscribe send an email to [email protected]
