From: Brian May <brian@microcomaustralia.com.au>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] searching buffer
Date: Tue, 16 Nov 2010 10:58:54 +1100 [thread overview]
Message-ID: <AANLkTi=N-Rbe9smXbmGaycDyAB49VKi4PV85=q4YoDG-@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik7-jqHqu+CSBeFXxVvBOdcytTJPisAGGwbkHbS@mail.gmail.com>
On 16 November 2010 10:54, Hamish D <dmishd@gmail.com> 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 <brian@microcomaustralia.com.au>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-11-16 0:46 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 [this message]
2010-11-16 16:40 ` David J. Hamilton
2010-11-16 22:30 ` Brian May
2010-11-17 4:38 ` David J. Hamilton
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='AANLkTi=N-Rbe9smXbmGaycDyAB49VKi4PV85=q4YoDG-@mail.gmail.com' \
--to=brian@microcomaustralia.com.au \
--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