Subject: [sup-talk] Should '/' trigger the loading of more messages?

From: [email-masked] (Carl Worth)
Date: Wed, 26 Aug 2009 15:47:54 -0700

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>

---

From: [email-masked] (Ingmar Vanhassel)
Date: Thu, 27 Aug 2009 04:37:57 +0200

> 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.

> message of interest wasn't loaded yet.

If you know it's in your inbox, why not search with '\', for
'label:inbox foo'?

> cancel or interrupt any ongoing command?

Try C-g. :-)
(Documented as ^G on the help page)

-- 
Exherbo KDE, X.org maintainer

---

From: [email-masked] (Marcus Williams)
Date: Thu, 27 Aug 2009 10:05:13 +0100

> If you know it's in your inbox, why not search with '\', for

... coupled with '!!' to load all threads in the search (ctrl-g works
to stop search) this would do what you want.

HTH

Marcus

---

From: [email-masked] (Carl Worth)
Date: Thu, 27 Aug 2009 05:17:12 -0700

> I'd expect a "search in current buffer" to do exactly that, no more no

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

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?

> (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>