From: David J. Hamilton <groups@hjdivad.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] searching buffer
Date: Tue, 16 Nov 2010 20:38:54 -0800 [thread overview]
Message-ID: <1289968347-sup-5996@nyx.local> (raw)
In-Reply-To: <AANLkTi=+SiM33JgeBpMHc=0Tm9zv4Ckw0dHt_SwMFDuf@mail.gmail.com>
Excerpts from Brian May's message of Tue Nov 16 14:30:09 -0800 2010:
> On 17 November 2010 03:40, David J. Hamilton <groups@hjdivad.com> 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
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-11-17 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 22:14 Brian May
[not found] ` <AANLkTik7-jqHqu+CSBeFXxVvBOdcytTJPisAGGwbkHbS@mail.gmail.com>
2010-11-15 23:58 ` Brian May
2010-11-16 16:40 ` David J. Hamilton
2010-11-16 22:30 ` Brian May
2010-11-17 4:38 ` David J. Hamilton [this message]
2010-11-16 0:16 ` Blake Sweeney
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=1289968347-sup-5996@nyx.local \
--to=groups@hjdivad.com \
--cc=sup-talk@rubyforge.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