From: David Bremner <david@tethera.net>
To: Ramakrishnan Muthukrishnan <ram@rkrishnan.org>, notmuch@notmuchmail.org
Subject: Re: search order
Date: Sun, 18 Aug 2013 16:32:18 +0200 [thread overview]
Message-ID: <87vc33oyrx.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <m2bo5c5h8l.fsf@ramakrmu-mac.i-did-not-set--mail-host-address--so-tickle-me>
Ramakrishnan Muthukrishnan <ram@rkrishnan.org> writes:
> If I startup notmuch and then do a M-x notmuch-search and then *, I see
> the messages with the newest on the top. But if I instead, startup
> notmuch and then hit "s", I see that the new messages are at the
> bottom. The value of notmuch-search-oldest-first is t.
I had a quick look at this, and I think the issue is as follows:
notmuch-search takes an extra parameter for the order, and does not
directly look at notmuch-search-oldest-first. notmuch-hello-search
works better in this case because it calls notmuch-search with
notmuch-search-oldest-first as one of it's parameters. The simplest
solution would be to make another helper function like
(defun notmuch-search-interactive ()
(interactive)
(notmuch-search nil notmuch-search-oldest-first))
I don't know if notmuch-search should remain interactive, or perhaps be
renamed and have interactive removed (with the new helper replacing it).
I guess that might break some user code.
d
next prev parent reply other threads:[~2013-08-18 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 14:45 search order Ramakrishnan Muthukrishnan
2013-08-18 14:32 ` David Bremner [this message]
2013-09-10 11:23 ` David Bremner
2013-09-10 14:28 ` Ramakrishnan Muthukrishnan
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=87vc33oyrx.fsf@maritornes.cs.unb.ca \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=ram@rkrishnan.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).