From: "Drew Adams" <drew.adams@oracle.com>
To: "'Alan Mackenzie'" <acm@muc.de>
Cc: 'Emacs-Devel devel' <emacs-devel@gnu.org>
Subject: RE: add non-chord keys to repeat isearch
Date: Tue, 9 Jun 2009 10:08:34 -0700 [thread overview]
Message-ID: <8D5E1C403AD94F20A406381F2679E64A@us.oracle.com> (raw)
In-Reply-To: <20090609164716.GA11634@muc.de>
> Please don't. These two keys are already used in Isearch Mode for
> scrolling. To see this, set `isearch-allow-scroll' to t. Then <next>
> and <prior> are handy keys for seeing more text around the
> match without having to leave isearch and start again.
(I wasn't aware of that option. I've just filed a bug to index it in the Emacs
manual.)
However, just because some binding was made previously (when someone first had
the idea of scrolling without exiting Isearch) is no reason not to reconsider
that binding in light of a better suggestion. Emacs is not purely
first-come-first-served.
`M-v' and `C-v' can be used for scrolling (when the option is non-nil).
And `<prior>' and `<next>' can be used for repeat search. There's room for all.
[BTW, scrolling during isearch doesn't seem to work beyond a single screen
height. Is that a bug or a feature? IOW, `C-s C-v C-v': the second `C-v' has no
effect.]
> The same applies to any keys bound to commands which have the
> `isearch-scroll' non-nil.
That's fine, but a specific key binding can override that. We can choose to bind
`<prior>' to `isearch-repeat-backward' even though `scroll-up' has non-nil
property `isearch-scroll'. Works fine. There is no need to sacrifice all keys
that might be bound globally to `scroll-up'.
next prev parent reply other threads:[~2009-06-09 17:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 15:44 add non-chord keys to repeat isearch Drew Adams
2009-06-09 15:51 ` Deniz Dogan
2009-06-09 15:59 ` Drew Adams
2009-06-09 16:47 ` Alan Mackenzie
2009-06-09 17:08 ` Drew Adams [this message]
2009-06-09 17:45 ` Deniz Dogan
2009-06-09 17:48 ` Alan Mackenzie
2009-06-09 18:27 ` Drew Adams
2009-06-09 19:56 ` Alan Mackenzie
2009-06-10 17:32 ` Drew Adams
2009-06-14 17:12 ` Alan Mackenzie
2009-06-09 23:06 ` Miles Bader
2009-06-10 17:32 ` Drew Adams
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=8D5E1C403AD94F20A406381F2679E64A@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.