mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-26 07:11:34 -08:00
(Changing Key Bindings): Cleanup.
Add xref to Key Binding Conventions.
This commit is contained in:
parent
c5a83cf9dd
commit
fc0804c447
1 changed files with 9 additions and 5 deletions
|
|
@ -1198,6 +1198,10 @@ convenient interfaces for these operations (@pxref{Key Binding
|
|||
Commands}). You can also use @code{define-key}, a more general
|
||||
function; then you must specify explicitly the map to change.
|
||||
|
||||
When choosing the key sequences for Lisp programs to rebind, please
|
||||
follow the Emacs conventions for use of various keys (@pxref{Key
|
||||
Binding Conventions}).
|
||||
|
||||
@cindex meta character key constants
|
||||
@cindex control character key constants
|
||||
In writing the key sequence to rebind, it is good to use the special
|
||||
|
|
@ -1219,11 +1223,11 @@ key name). For example, @code{(control ?a)} is equivalent to
|
|||
@code{C-H-left}. One advantage of such lists is that the precise
|
||||
numeric codes for the modifier bits don't appear in compiled files.
|
||||
|
||||
For the functions below, an error is signaled if @var{keymap} is not
|
||||
a keymap or if @var{key} is not a string or vector representing a key
|
||||
sequence. You can use event types (symbols) as shorthand for events
|
||||
that are lists. The @code{kbd} macro (@pxref{Key Sequences}) is a
|
||||
convenient way to specify the key sequence.
|
||||
The functions below signal an error if @var{keymap} is not a keymap,
|
||||
or if @var{key} is not a string or vector representing a key sequence.
|
||||
You can use event types (symbols) as shorthand for events that are
|
||||
lists. The @code{kbd} macro (@pxref{Key Sequences}) is a convenient
|
||||
way to specify the key sequence.
|
||||
|
||||
@defun define-key keymap key binding
|
||||
This function sets the binding for @var{key} in @var{keymap}. (If
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue