From: cworth@cworth.org (Carl Worth)
Subject: [sup-talk] Should '/' trigger the loading of more messages?
Date: Thu, 27 Aug 2009 05:17:12 -0700 [thread overview]
Message-ID: <1251375048-sup-403@yoom.home.cworth.org> (raw)
In-Reply-To: <1251340454-sup-3773@cannonball>
Excerpts from Ingmar Vanhassel's message of Wed Aug 26 19:37:57 -0700 2009:
> Excerpts from Carl Worth's message of Thu Aug 27 00:47:54 +0200 2009:
> > It seems to me that the "search in current buffer" command should
> > automatically trigger the loading of additional messages when no
> > results are found so that it can continue searching.
>
> I'd expect a "search in current buffer" to do exactly that, no more no
> less.
You obviously know well what the current buffer is doing,
(incrementally loading threads only as you page down to them). But I
don't think it's reasonable to expect all users to understand things
that well in order to use sup correctly.
Imagine the near future where we get the thread-loading performance
bugs all worked out, (see nearby threads making good progress). If a
user starts sup and sees a screenful of threads instantly, hits page
down a couple of times and sees another couple of screensful
instantly, then wouldn't it be reasonable for such a user to expect
that all of that instantly-appearing content does exist in the current
buffer?
> If you know it's in your inbox, why not search with '\', for
> 'label:inbox foo'?
I'm searching locally, because I already performed a global search and
don't want to repeat the terms of it. Or else why does sup have a
local search command independent of the global search?
> Try C-g. :-)
> (Documented as ^G on the help page)
Ah, thanks. Now this one was just me being stupid. (I think I was
already using this in sup naturally.)
-Carl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090827/cb5aaa58/attachment.bin>
prev parent reply other threads:[~2009-08-27 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 22:47 Carl Worth
2009-08-27 2:37 ` Ingmar Vanhassel
2009-08-27 9:05 ` Marcus Williams
2009-08-27 12:17 ` Carl Worth [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1251375048-sup-403@yoom.home.cworth.org \
--to=cworth@cworth.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox