From: "Drew Adams" <drew.adams@oracle.com>
To: "'Elena'" <egarrulo@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: one shortcut next occurrence search
Date: Fri, 24 Dec 2010 08:39:35 -0800 [thread overview]
Message-ID: <F44C78AED7664BCAA97BC73885342699@us.oracle.com> (raw)
In-Reply-To: <069984a0-048f-4cf8-bd94-250e8035c08b@j25g2000yqa.googlegroups.com>
> I didn't know about the "C-h b". What's the difference? Why I have
> to type "C-c C-h", "C-x C-h", etc. but "C-s C-h" does not work whilst
> "C-s C-h b" does?
Someone(TM)'s infinite wisdom. See my earlier message.
> Funnily enough, according to "C-h c", "C-c C-h" and "C-x C-h" are not
> bound to anything, neither is "C-h" alone (it is a prefix key).
Yes, things like `C-c' are sometimes handled specially to get the `C-h'
behavior. `C-h' does not show up on the keymap (which in the case of `C-c' is
`mode-specific-map'). Try `C-h M-k' and you will see.
next prev parent reply other threads:[~2010-12-24 16:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 8:20 one shortcut next occurrence search zismad
2010-12-23 3:03 ` Drew Adams
2010-12-23 7:22 ` zismad
2010-12-23 8:29 ` Tassilo Horn
2010-12-23 13:26 ` zismad
2010-12-23 13:50 ` Tassilo Horn
2010-12-23 9:17 ` Eli Zaretskii
2010-12-23 17:12 ` Drew Adams
[not found] ` <mailman.1.1293088974.1406.help-gnu-emacs@gnu.org>
2010-12-23 13:39 ` Vagn Johansen
[not found] ` <mailman.16.1293073448.15570.help-gnu-emacs@gnu.org>
2010-12-24 9:44 ` rusi
2010-12-24 10:18 ` Teemu Likonen
2010-12-24 10:36 ` Elena
2010-12-24 10:51 ` Tassilo Horn
2010-12-24 16:39 ` Drew Adams
[not found] ` <mailman.0.1293187918.15516.help-gnu-emacs@gnu.org>
2010-12-24 11:17 ` Elena
2010-12-24 11:27 ` Elena
2010-12-24 16:39 ` Drew Adams [this message]
2010-12-24 11:27 ` Richard Riley
2010-12-25 16:37 ` Bob Proulx
[not found] <mailman.10.1293068065.15570.help-gnu-emacs@gnu.org>
2010-12-23 9:31 ` Elena
2010-12-23 22:06 ` LanX
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=F44C78AED7664BCAA97BC73885342699@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=egarrulo@gmail.com \
--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.