From: James Vasile <james@hackervisions.org>
To: Michal Sojka <sojkam1@fel.cvut.cz>, notmuch@notmuchmail.org
Subject: Re: [PATCH] Return maximum of 150 results
Date: Fri, 19 Aug 2011 11:37:54 -0400 [thread overview]
Message-ID: <87r54hv2ct.fsf@opensourcematters.org> (raw)
In-Reply-To: <87mxf5v43c.fsf@steelpick.2x.cz>
On Fri, 19 Aug 2011 17:00:23 +0200, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
> Hi James,
>
> On Fri, 19 Aug 2011, James Vasile wrote:
> > Display a maximum of 150 results when searching for messages. This
> > prevents client lag when searches return thousands of results you'll
> > never look at
>
> I would not like this feature. If I search for something I really want
> to see everything. For example, if I want to remove inbox from many
> messages, I would search for them and press "-inbox<ret>". With your
> patch I'd not be sure whether there are some more messages or not.
Ah, I do such things from the commandline, but you are right that there
is a good use for such.
>
> > (use the Filter command to cut down results that exceed 150).
>
> You can start filtering while the previous search is still running, so I
> do not see problem with having bug number of results.
Yes, you can filter while the search runs, but that's not the only
problem with huge search results. On my system, I routinely do searches
that return 15000+ messages when I'm only interested in the first
several. When I hit Q, Emacs annoyingly asks me for permission to kill
the buffer because it has a running process. And emacs lags as it
processes all that data.
> >
> > Number of results can be changed by setting notmuch-max-results.
>
> If you really want this behavior, I propose to make the default value
> of notmuch-max-results infinity.
Yes, that's probably the right answer. I'll rework the patch to do that.
next prev parent reply other threads:[~2011-08-19 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 3:15 [PATCH] Return maximum of 150 results James Vasile
2011-08-19 15:00 ` Michal Sojka
2011-08-19 15:37 ` James Vasile [this message]
2011-08-19 16:00 ` Michal Sojka
2011-08-19 16:30 ` James Vasile
2011-08-19 18:30 ` Jameson Graef Rollins
2011-08-20 19:11 ` James Vasile
2011-08-22 23:46 ` Daniel Schoepe
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=87r54hv2ct.fsf@opensourcematters.org \
--to=james@hackervisions.org \
--cc=notmuch@notmuchmail.org \
--cc=sojkam1@fel.cvut.cz \
/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).