From: "seberino@spawar.navy.mil" <seberino@spawar.navy.mil>
To: help-gnu-emacs@gnu.org
Subject: Why function behaves differently when bound to different key combo?
Date: Thu, 27 Nov 2008 20:38:19 -0800 (PST) [thread overview]
Message-ID: <6daf5632-fd9e-4ade-a2d3-b23ca738f9da@r37g2000prr.googlegroups.com> (raw)
Normally incremental search can be repeated by pressing C-s multiple
times.
Why if I remap incremental search to C-f I CANNOT repeat it by
pressing C-f multiple times?....
Here is how I remapped it...
(global-set-key "\^f" 'isearch-forward)
chris
next reply other threads:[~2008-11-28 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 4:38 seberino [this message]
2008-11-28 6:22 ` Why function behaves differently when bound to different key combo? Phil Carmody
2008-11-28 6:28 ` Andy Stewart
2008-11-28 14:00 ` Xah Lee
2008-11-28 20:54 ` isearch key bindings [was: Why function behaves differently when bound to different key combo?] Alan Mackenzie
[not found] ` <mailman.1453.1227904853.26697.help-gnu-emacs@gnu.org>
2008-11-30 2:38 ` Xah Lee
2008-11-30 15:22 ` Kevin Rodgers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6daf5632-fd9e-4ade-a2d3-b23ca738f9da@r37g2000prr.googlegroups.com \
--to=seberino@spawar.navy.mil \
--cc=help-gnu-emacs@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).