[Emacs-diffs] Changes to emacs/lispref/keymaps.texi [lexbind]

[Miles Bader]

Index: emacs/lispref/keymaps.texi
diff -c emacs/lispref/keymaps.texi:1.39.4.2 emacs/lispref/keymaps.texi:1.39.4.3
*** emacs/lispref/keymaps.texi:1.39.4.2 Tue Oct 14 19:10:12 2003
--- emacs/lispref/keymaps.texi  Thu Nov 20 19:35:46 2003
***************
*** 231,239 ****
  @defun make-keymap &optional prompt
  This function creates and returns a new full keymap.  That keymap
  contains a char-table (@pxref{Char-Tables}) with 384 slots: the first
! 128 slots are for defining all the @sc{ascii} characters, the next 128
  slots are for 8-bit European characters, and each one of the final 128
! slots is for one character set of address@hidden characters supported by
  Emacs.  The new keymap initially binds all these characters to
  @code{nil}, and does not bind any other kind of event.
  
--- 231,239 ----
  @defun make-keymap &optional prompt
  This function creates and returns a new full keymap.  That keymap
  contains a char-table (@pxref{Char-Tables}) with 384 slots: the first
! 128 slots are for defining all the @acronym{ASCII} characters, the next 128
  slots are for 8-bit European characters, and each one of the final 128
! slots is for one character set of address@hidden characters supported by
  Emacs.  The new keymap initially binds all these characters to
  @code{nil}, and does not bind any other kind of event.
  
***************
*** 593,599 ****
  This function returns the current buffer's local keymap, or @code{nil}
  if it has none.  In the following example, the keymap for the
  @samp{*scratch*} buffer (using Lisp Interaction mode) is a sparse keymap
! in which the entry for @key{ESC}, @sc{ascii} code 27, is another sparse
  keymap.
  
  @example
--- 593,599 ----
  This function returns the current buffer's local keymap, or @code{nil}
  if it has none.  In the following example, the keymap for the
  @samp{*scratch*} buffer (using Lisp Interaction mode) is a sparse keymap
! in which the entry for @key{ESC}, @acronym{ASCII} code 27, is another sparse
  keymap.
  
  @example
***************
*** 999,1005 ****
  translating a meta character to a two-character sequence so it can be
  looked up in a keymap.  For useful results, the value should be a prefix
  event (@pxref{Prefix Keys}).  The default value is 27, which is the
! @sc{ascii} code for @key{ESC}.
  
  As long as the value of @code{meta-prefix-char} remains 27, key lookup
  translates @kbd{M-b} into @address@hidden b}, which is normally defined
--- 999,1005 ----
  translating a meta character to a two-character sequence so it can be
  looked up in a keymap.  For useful results, the value should be a prefix
  event (@pxref{Prefix Keys}).  The default value is 27, which is the
! @acronym{ASCII} code for @key{ESC}.
  
  As long as the value of @code{meta-prefix-char} remains 27, key lookup
  translates @kbd{M-b} into @address@hidden b}, which is normally defined
***************
*** 1361,1368 ****
  redefines the first (leftmost) mouse button, typed with the Meta key, to
  set point where you click.
  
! @cindex address@hidden text in keybindings
!   Be careful when using address@hidden text characters in Lisp
  specifications of keys to bind.  If these are read as multibyte text, as
  they usually will be in a Lisp file (@pxref{Loading Non-ASCII}), you
  must type the keys as multibyte too.  For instance, if you use this:
--- 1361,1368 ----
  redefines the first (leftmost) mouse button, typed with the Meta key, to
  set point where you click.
  
! @cindex address@hidden text in keybindings
!   Be careful when using address@hidden text characters in Lisp
  specifications of keys to bind.  If these are read as multibyte text, as
  they usually will be in a Lisp file (@pxref{Loading Non-ASCII}), you
  must type the keys as multibyte too.  For instance, if you use this:
***************
*** 1576,1582 ****
  string representing the first key sequence found, rather than a list of
  all possible key sequences.  If @var{firstonly} is @code{t}, then the
  value is the first key sequence, except that key sequences consisting
! entirely of @sc{ascii} characters (or meta variants of @sc{ascii}
  characters) are preferred to all other key sequences.
  
  If @var{noindirect} is address@hidden, @code{where-is-internal} doesn't
--- 1576,1582 ----
  string representing the first key sequence found, rather than a list of
  all possible key sequences.  If @var{firstonly} is @code{t}, then the
  value is the first key sequence, except that key sequences consisting
! entirely of @acronym{ASCII} characters (or meta variants of @acronym{ASCII}
  characters) are preferred to all other key sequences.
  
  If @var{noindirect} is address@hidden, @code{where-is-internal} doesn't
***************
*** 1609,1621 ****
  The listing describes meta characters as @key{ESC} followed by the
  corresponding non-meta character.
  
! When several characters with consecutive @sc{ascii} codes have the
  same definition, they are shown together, as
  @address@hidden@var{lastchar}}.  In this instance, you need to
! know the @sc{ascii} codes to understand which characters this means.
  For example, in the default global map, the characters @address@hidden
! ..@: ~} are described by a single line.  @key{SPC} is @sc{ascii} 32,
! @kbd{~} is @sc{ascii} 126, and the characters between them include all
  the normal printing characters, (e.g., letters, digits, punctuation,
  etc.@:); all these characters are bound to @code{self-insert-command}.
  @end deffn
--- 1609,1621 ----
  The listing describes meta characters as @key{ESC} followed by the
  corresponding non-meta character.
  
! When several characters with consecutive @acronym{ASCII} codes have the
  same definition, they are shown together, as
  @address@hidden@var{lastchar}}.  In this instance, you need to
! know the @acronym{ASCII} codes to understand which characters this means.
  For example, in the default global map, the characters @address@hidden
! ..@: ~} are described by a single line.  @key{SPC} is @acronym{ASCII} 32,
! @kbd{~} is @acronym{ASCII} 126, and the characters between them include all
  the normal printing characters, (e.g., letters, digits, punctuation,
  etc.@:); all these characters are bound to @code{self-insert-command}.
  @end deffn
***************
*** 1695,1701 ****
  The @sc{car}, @var{item-string}, is the string to be displayed in the
  menu.  It should be short---preferably one to three words.  It should
  describe the action of the command it corresponds to.  Note that it is
! not generally possible to display non-ASCII text in menus.  It will
  work for keyboard menus and will work to a large extent when Emacs is
  built with Gtk+ address@hidden this case, the text is first
  encoded using the @code{utf-8} coding system and then rendered by the
--- 1695,1701 ----
  The @sc{car}, @var{item-string}, is the string to be displayed in the
  menu.  It should be short---preferably one to three words.  It should
  describe the action of the command it corresponds to.  Note that it is
! not generally possible to display address@hidden text in menus.  It will
  work for keyboard menus and will work to a large extent when Emacs is
  built with Gtk+ address@hidden this case, the text is first
  encoded using the @code{utf-8} coding system and then rendered by the