From: cworth@cworth.org (Carl Worth)
Subject: [sup-talk] Should '/' trigger the loading of more messages?
Date: Wed, 26 Aug 2009 15:47:54 -0700 [thread overview]
Message-ID: <1251326494-sup-2328@yoom.home.cworth.org> (raw)
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.
What just happened to me is that I *knew* my inbox contained a message
with a particular string in the subject, but I couldn't find it with
'/'. The problem was that enough new threads had arrived that the
message of interest wasn't loaded yet.
The fact that the various ThreadIndexModes don't load all relevant
threads is just an optimization, but I don't think it should change
the semantics of a search operation. (My thread *is* still in my inbox
even if it hasn't been loaded.)
Of course, for the feature I want to work well there needs to be an
easy way to interrupt the searching and loading if it's going on too
long, (say, I mistyped the search string and I know it's likely to
load a million messages without ever finding the string I typed).
Does sup already have a notion like emacs' "C-g" which is used to
cancel or interrupt any ongoing command?
-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/20090826/5445e913/attachment.bin>
next reply other threads:[~2009-08-26 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 22:47 Carl Worth [this message]
2009-08-27 2:37 ` Ingmar Vanhassel
2009-08-27 9:05 ` Marcus Williams
2009-08-27 12:17 ` Carl Worth
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=1251326494-sup-2328@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