From: James Vasile <james@hackervisions.org>
To: Patrick Totzke <patricktotzke@googlemail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH] Added --initial-index and --last-index to search/show
Date: Sat, 20 Aug 2011 08:39:42 -0400 [thread overview]
Message-ID: <87ty9ctfxt.fsf@softwarefreedom.org> (raw)
In-Reply-To: <4e4f98b9.0806e30a.0505.ffffbdb3@mx.google.com>
On Sat, 20 Aug 2011 12:21:26 +0100, Patrick Totzke <patricktotzke@googlemail.com> wrote:
Non-text part: multipart/mixed
>
>
> Hi!
> A very good idea indeed! This could become quite handy speeding up my interface.
> One question: What do you (intend to) do to ensure that accumulated results
> 'add up well'?
I intend to do nothing. It's up to the interface to handle this, if it
needs handling at all.
> Consider the following: you query some 10 threads, the user tags one of them
> so that it doesn't macht anymore and afterwards you list the next 100 threads.
> After the tagging, the number of hits decreases, so if you query
> from hit number 101 to 200, you will not return the 100th (now 99th)
> thread at all.
The interface could keep track of threads deleted/untagged and adjust
accordingly.
Or I suppose one could also implement --initial-msgid, --last-msgid,
--num-threads, etc. Set --initial-msgid to the last message in your
current view. Set --num-threads to 100. That should do it.
>
> Ok, one could always list all threads up to the one one is interested in but that
> would make refreshing the list slower and slower when you keep
> scrolling down..
Personally, I think users should be discouraged from scrolling and
scrolling. Notmuch is a *search* tool. If the mail you want isn't in
the first page or so, you're using the tool wrong.
-J
prev parent reply other threads:[~2011-08-20 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 3:09 [PATCH] Added --initial-index and --last-index to search/show James Vasile
2011-08-19 18:55 ` Jameson Graef Rollins
2011-08-19 19:36 ` James Vasile
2011-08-20 11:21 ` Patrick Totzke
2011-08-20 12:39 ` James Vasile [this message]
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=87ty9ctfxt.fsf@softwarefreedom.org \
--to=james@hackervisions.org \
--cc=notmuch@notmuchmail.org \
--cc=patricktotzke@googlemail.com \
/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).