Subject: Re: [sup-talk] searching buffer

From: Brian May <[email-masked]>
Date: Tue, 16 Nov 2010 10:58:54 +1100

On 16 November 2010 10:54, Hamish D <[email-masked]> wrote:
> Press enter to end the search, then press 'n' to go through subsequent
> matches.

Doesn't work. Instead of going to the next search results, it hides
the results of the last search.

Furthermore, the help on my system says n has a different function:

       n : Jump to next open message

-- 
Brian May <[email-masked]>
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Brian May <[email-masked]>
Date: Tue, 16 Nov 2010 09:14:23 +1100

Hello,

When viewing a message, I can use "/text" to search for the first
instance of "text" in the buffer.

How do I repeat this and find the 2nd or even 3rd instance of "text"?

Thanks

---

From: Blake Sweeney <[email-masked]>
Date: Mon, 15 Nov 2010 19:16:10 -0500

> How do I repeat this and find the 2nd or even 3rd instance of "text"?

I use 'n'.

Blake

---

From: David J. Hamilton <[email-masked]>
Date: Tue, 16 Nov 2010 20:38:54 -0800

Excerpts from Brian May's message of Tue Nov 16 14:30:09 -0800 2010:
> On 17 November 2010 03:40, David J. Hamilton <[email-masked]> wrote:
> > You might want to retry with all of the messages open.  The search feature seems
> > to really only search the buffer, and not the “collapsed” text (e.g. message
> > body text in a closed message).  The same applies to hitting ‘n’ to advance to
> > the next search result.
> 
> Yes, tried that.
> 
> Like I said, 'n' hides all the existing search results.

In that case, my local copy of sup (v0.11 on ruby 1.8.7) is just behaving
differently from yours for some reason.  If I search for text using ‘/’,
subsequently hitting ‘n’ moves to the next instance.  However, if I hit
something like ‘j’ or ‘k’ then the search is unhighlighted and ‘n’ switches back
to its “Jump to next open message” function.

The only other thing I can think of is that when I run a search in a buffer that has
no results, ‘n’ never changes from its “Jump to next open message” function.

In any case, if somebody more knowledgeable than me gets to your question,
hopefully they can shed some light on how one can do a search (in a thread
buffer) of an entire thread's content, and not merely the content of the open
messages.

-- 
med vänlig hälsning
David J. Hamilton

---

From: Brian May <[email-masked]>
Date: Wed, 17 Nov 2010 09:30:09 +1100

Yes, tried that.

'n' would appear to map to the "Jump to next open message" function,
not the "find next search result" function.
-- 
Brian May <[email-masked]>
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: David J. Hamilton <[email-masked]>
Date: Tue, 16 Nov 2010 08:40:01 -0800