From: ingmar@exherbo.org (Ingmar Vanhassel)
Subject: [sup-talk] Should '/' trigger the loading of more messages?
Date: Thu, 27 Aug 2009 04:37:57 +0200 [thread overview]
Message-ID: <1251340454-sup-3773@cannonball> (raw)
In-Reply-To: <1251326494-sup-2328@yoom.home.cworth.org>
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.
> 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.
If you know it's in your inbox, why not search with '\', for
'label:inbox foo'?
> 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?
Try C-g. :-)
(Documented as ^G on the help page)
> -Carl
--
Exherbo KDE, X.org maintainer
next prev parent reply other threads:[~2009-08-27 2:37 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 [this message]
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=1251340454-sup-3773@cannonball \
--to=ingmar@exherbo.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