all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jim Green <student.northwestern@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: find out in which file a key is defined
Date: Wed, 7 Dec 2011 23:34:29 +0000	[thread overview]
Message-ID: <CACAe89x_WCtpCY0HJP7WTRT=1SULX9Gqspx8vd3emYA0WjODDQ@mail.gmail.com> (raw)
In-Reply-To: <87iplsogud.fsf@ericabrahamsen.net>

On 7 December 2011 09:45, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> On Wed, Dec 07 2011, Jim Green wrote:
>
>> Hello:
>>
>> Could anyone help on this question from an emacs learner:
>>
>> is there a command to find out why c-r is defined as isearch-backward?
>> and how to disable this behavior?
>>
>> Thanks!
>>
>> Jim.
>>
>> below is obtained by c-h k c-r
>
> When I run that command it tells me that the key is defined in
> isearch.el (I'm running emacs 24). That's the facile answer to "why",

thank you both, this what I get by c-h k c-r, but where could I find it
is from isearch.el? I think finding where a key defined is very useful.

C-r runs the command isearch-backward, which is an interactive
compiled Lisp function.

It is bound to C-r, <menu-bar> <edit> <search> <i-search>
<isearch-backward>.

(isearch-backward &optional REGEXP-P NO-RECURSIVE-EDIT)

Do incremental search backward.
With a prefix argument, do a regular expression search instead.
See the command `isearch-forward' for more information.


Thanks, Jim



  reply	other threads:[~2011-12-07 23:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07  3:52 find out in which file a key is defined Jim Green
2011-12-07  6:35 ` Jambunathan K
2011-12-07  9:45 ` Eric Abrahamsen
2011-12-07 23:34   ` Jim Green [this message]
2011-12-08  0:20     ` suvayu ali
2011-12-08  0:23       ` Jim Green

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='CACAe89x_WCtpCY0HJP7WTRT=1SULX9Gqspx8vd3emYA0WjODDQ@mail.gmail.com' \
    --to=student.northwestern@gmail.com \
    --cc=eric@ericabrahamsen.net \
    --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.
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.