From: eyal.oren@deri.org (Eyal Oren)
Subject: [sup-talk] new in svn: in-buffer search
Date: Wed, 07 Nov 2007 10:21:57 +0100 [thread overview]
Message-ID: <1194427158-sup-6839@timmy> (raw)
In-Reply-To: <1194425266-sup-7682@tomsk>
Excerpts from Marcus Williams's message of Wed Nov 07 09:53:35 +0100 2007:
> On 6.11.2007, William Morgan wrote:
> > First, note that I've remapped the index search from '/' to '\'. Hah!
> >
> > '/' now does an in-buffer search, highlights the results, and jumps to
> > the first one. 'n' jumps to the next result; ^G or any other key cancels
> > the current search.
>
> This feels a bit wrong to me (might just be me though). I'd say that
> searching for emails is the most used case for a search option in sup
> so should have the '/', and searching in buffer should be something
> different.
>
> Better than that, make '/' mode dependant so you can use say ctrl-s to
> search for emails (always), ctrl-f to search in buffer (always) but
> map '/' to ctrl-s in thread-index mode (so that would be in inbox and
> search results). In all other modes '/' could map to ctrl-f.
Personally, I feel that '/' should search in buffer, as many other UNIX tools do
(vi, mutt, less, etc).
Btw, William, thanks for the search! It's great. But wouldn't you like to search
from the top instead of searching from cursor position? I often want to use
search instead of hitting cursor-up seven times.
--
-eyal
next prev parent reply other threads:[~2007-11-07 9:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 22:41 William Morgan
2007-11-06 22:57 ` Ian Taylor
2007-11-07 0:18 ` William Morgan
2007-11-07 8:53 ` Marcus Williams
2007-11-07 9:21 ` Eyal Oren [this message]
2007-11-07 9:43 ` Marcus Williams
2007-11-07 9:53 ` Marcus Williams
2007-11-12 0:13 ` William Morgan
2007-11-07 14:25 ` vasudeva
2007-11-07 20:41 ` William Morgan
2007-11-07 21:05 ` Marcus Williams
2007-11-12 0:11 ` William Morgan
2007-11-07 21:56 ` Colin Bell
2007-11-12 0:02 ` William Morgan
2007-11-12 0:33 ` Christopher Warrington
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=1194427158-sup-6839@timmy \
--to=eyal.oren@deri.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