emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] Changes to emacs/man/custom.texi [lexbind]


From: Miles Bader
Subject: [Emacs-diffs] Changes to emacs/man/custom.texi [lexbind]
Date: Thu, 20 Nov 2003 19:36:52 -0500

Index: emacs/man/custom.texi
diff -c emacs/man/custom.texi:1.48.2.2 emacs/man/custom.texi:1.48.2.3
*** emacs/man/custom.texi:1.48.2.2      Tue Oct 14 18:56:22 2003
--- emacs/man/custom.texi       Thu Nov 20 19:36:12 2003
***************
*** 1081,1087 ****
  * Init Rebinding::      Rebinding keys with your init file, @file{.emacs}.
  * Function Keys::       Rebinding terminal function keys.
  * Named ASCII Chars::   Distinguishing @key{TAB} from @kbd{C-i}, and so on.
! * Non-ASCII Rebinding:: Rebinding non-ASCII characters such as Latin-1.
  * Mouse Buttons::       Rebinding mouse buttons in Emacs.
  * Disabling::           Disabling a command means confirmation is required
                            before it can be executed.  This is done to protect
--- 1081,1087 ----
  * Init Rebinding::      Rebinding keys with your init file, @file{.emacs}.
  * Function Keys::       Rebinding terminal function keys.
  * Named ASCII Chars::   Distinguishing @key{TAB} from @kbd{C-i}, and so on.
! * Non-ASCII Rebinding:: Rebinding address@hidden characters such as Latin-1.
  * Mouse Buttons::       Rebinding mouse buttons in Emacs.
  * Disabling::           Disabling a command means confirmation is required
                            before it can be executed.  This is done to protect
***************
*** 1405,1412 ****
  you can specify them in your @file{.emacs} file by using their Lisp
  syntax.  (@xref{Init File}.)
  
!   The simplest method for doing this works for ASCII characters and
! Meta-modified ASCII characters only.  This method uses a string to
  represent the key sequence you want to rebind.  For example, here's how
  to bind @kbd{C-z} to @code{shell}:
  
--- 1405,1412 ----
  you can specify them in your @file{.emacs} file by using their Lisp
  syntax.  (@xref{Init File}.)
  
!   The simplest method for doing this works for @acronym{ASCII} characters and
! Meta-modified @acronym{ASCII} characters only.  This method uses a string to
  represent the key sequence you want to rebind.  For example, here's how
  to bind @kbd{C-z} to @code{shell}:
  
***************
*** 1436,1442 ****
  (global-set-key "\C-x\t" 'indent-rigidly)
  @end example
  
!   These examples show how to write some other special ASCII characters
  in strings for key bindings:
  
  @example
--- 1436,1442 ----
  (global-set-key "\C-x\t" 'indent-rigidly)
  @end example
  
!   These examples show how to write some other special @acronym{ASCII} 
characters
  in strings for key bindings:
  
  @example
***************
*** 1446,1452 ****
  @end example
  
    When the key sequence includes function keys or mouse button events,
! or non-ASCII characters such as @code{C-=} or @code{H-a}, you must use
  the more general method of rebinding, which uses a vector to specify the
  key sequence.
  
--- 1446,1452 ----
  @end example
  
    When the key sequence includes function keys or mouse button events,
! or address@hidden characters such as @code{C-=} or @code{H-a}, you must use
  the more general method of rebinding, which uses a vector to specify the
  key sequence.
  
***************
*** 1458,1465 ****
  the character as it would appear in a string.
  
    Here are examples of using vectors to rebind @kbd{C-=} (a control
! character not in ASCII), @kbd{C-M-=} (not in ASCII because @kbd{C-=}
! is not), @kbd{H-a} (a Hyper character; ASCII doesn't have Hyper at
  all), @key{F7} (a function key), and @kbd{C-Mouse-1} (a
  keyboard-modified mouse button):
  
--- 1458,1465 ----
  the character as it would appear in a string.
  
    Here are examples of using vectors to rebind @kbd{C-=} (a control
! character not in @acronym{ASCII}), @kbd{C-M-=} (not in @acronym{ASCII} 
because @kbd{C-=}
! is not), @kbd{H-a} (a Hyper character; @acronym{ASCII} doesn't have Hyper at
  all), @key{F7} (a function key), and @kbd{C-Mouse-1} (a
  keyboard-modified mouse button):
  
***************
*** 1490,1496 ****
  delimit the vector.
  
    Language and coding systems can cause problems with key bindings
! for non-ASCII characters.  @xref{Non-ASCII Rebinding}.
  
  @node Function Keys
  @subsection Rebinding Function Keys
--- 1490,1496 ----
  delimit the vector.
  
    Language and coding systems can cause problems with key bindings
! for address@hidden characters.  @xref{Non-ASCII Rebinding}.
  
  @node Function Keys
  @subsection Rebinding Function Keys
***************
*** 1535,1541 ****
  key.
  
    A key sequence which contains function key symbols (or anything but
! ASCII characters) must be a vector rather than a string.  The vector
  syntax uses spaces between the elements, and square brackets around the
  whole vector.  Thus, to bind function key @samp{f1} to the command
  @code{rmail}, write the following:
--- 1535,1541 ----
  key.
  
    A key sequence which contains function key symbols (or anything but
! @acronym{ASCII} characters) must be a vector rather than a string.  The vector
  syntax uses spaces between the elements, and square brackets around the
  whole vector.  Thus, to bind function key @samp{f1} to the command
  @code{rmail}, write the following:
***************
*** 1583,1592 ****
  @end example
  
  @node Named ASCII Chars
! @subsection Named ASCII Control Characters
  
    @key{TAB}, @key{RET}, @key{BS}, @key{LFD}, @key{ESC} and @key{DEL}
! started out as names for certain ASCII control characters, used so often
  that they have special keys of their own.  Later, users found it
  convenient to distinguish in Emacs between these keys and the ``same''
  control characters typed with the @key{CTRL} key.
--- 1583,1592 ----
  @end example
  
  @node Named ASCII Chars
! @subsection Named @acronym{ASCII} Control Characters
  
    @key{TAB}, @key{RET}, @key{BS}, @key{LFD}, @key{ESC} and @key{DEL}
! started out as names for certain @acronym{ASCII} control characters, used so 
often
  that they have special keys of their own.  Later, users found it
  convenient to distinguish in Emacs between these keys and the ``same''
  control characters typed with the @key{CTRL} key.
***************
*** 1595,1619 ****
  reports these keys to Emacs.  It treats the ``special'' keys as function
  keys named @code{tab}, @code{return}, @code{backspace}, @code{linefeed},
  @code{escape}, and @code{delete}.  These function keys translate
! automatically into the corresponding ASCII characters @emph{if} they
  have no bindings of their own.  As a result, neither users nor Lisp
  programs need to pay attention to the distinction unless they care to.
  
    If you do not want to distinguish between (for example) @key{TAB} and
! @kbd{C-i}, make just one binding, for the ASCII character @key{TAB}
  (octal code 011).  If you do want to distinguish, make one binding for
! this ASCII character, and another for the ``function key'' @code{tab}.
  
!   With an ordinary ASCII terminal, there is no way to distinguish
  between @key{TAB} and @kbd{C-i} (and likewise for other such pairs),
  because the terminal sends the same character in both cases.
  
  @node Non-ASCII Rebinding
! @subsection Non-ASCII Characters on the Keyboard
! @cindex rebinding non-ASCII keys
! @cindex non-ASCII keys, binding
  
! If your keyboard has keys that send non-ASCII characters, such as
  accented letters, rebinding these keys is a bit tricky.  There are two
  solutions you can use.  One is to specify a keyboard coding system,
  using @code{set-keyboard-coding-system} (@pxref{Specify Coding}).
--- 1595,1619 ----
  reports these keys to Emacs.  It treats the ``special'' keys as function
  keys named @code{tab}, @code{return}, @code{backspace}, @code{linefeed},
  @code{escape}, and @code{delete}.  These function keys translate
! automatically into the corresponding @acronym{ASCII} characters @emph{if} they
  have no bindings of their own.  As a result, neither users nor Lisp
  programs need to pay attention to the distinction unless they care to.
  
    If you do not want to distinguish between (for example) @key{TAB} and
! @kbd{C-i}, make just one binding, for the @acronym{ASCII} character @key{TAB}
  (octal code 011).  If you do want to distinguish, make one binding for
! this @acronym{ASCII} character, and another for the ``function key'' 
@code{tab}.
  
!   With an ordinary @acronym{ASCII} terminal, there is no way to distinguish
  between @key{TAB} and @kbd{C-i} (and likewise for other such pairs),
  because the terminal sends the same character in both cases.
  
  @node Non-ASCII Rebinding
! @subsection address@hidden Characters on the Keyboard
! @cindex rebinding address@hidden keys
! @cindex address@hidden keys, binding
  
! If your keyboard has keys that send address@hidden characters, such as
  accented letters, rebinding these keys is a bit tricky.  There are two
  solutions you can use.  One is to specify a keyboard coding system,
  using @code{set-keyboard-coding-system} (@pxref{Specify Coding}).
***************
*** 1629,1635 ****
  @noindent
  Type @kbd{C-q} followed by the key you want to bind, to insert @var{char}.
  
! Since this puts a non-ASCII character in the @file{.emacs}, you should
  specify the proper coding system for that file.  @xref{Init Syntax}.
  Specify the same coding system for the file that you use for your
  keyboard.
--- 1629,1635 ----
  @noindent
  Type @kbd{C-q} followed by the key you want to bind, to insert @var{char}.
  
! Since this puts a address@hidden character in the @file{.emacs}, you should
  specify the proper coding system for that file.  @xref{Init Syntax}.
  Specify the same coding system for the file that you use for your
  keyboard.
***************
*** 1868,1875 ****
  characters that result from keyboard translation.
  
    On a window system, the keyboard key named @key{DELETE} is a function
! key and is distinct from the ASCII character named @key{DEL}.
! @xref{Named ASCII Chars}.  Keyboard translations affect only ASCII
  character input, not function keys; thus, the above example used on a
  window system does not affect the @key{DELETE} key.  However, the
  translation above isn't necessary on window systems, because Emacs can
--- 1868,1875 ----
  characters that result from keyboard translation.
  
    On a window system, the keyboard key named @key{DELETE} is a function
! key and is distinct from the @acronym{ASCII} character named @key{DEL}.
! @xref{Named ASCII Chars}.  Keyboard translations affect only @acronym{ASCII}
  character input, not function keys; thus, the above example used on a
  window system does not affect the @key{DELETE} key.  However, the
  translation above isn't necessary on window systems, because Emacs can
***************
*** 2002,2018 ****
  sequences are mandatory.
  
  @samp{\C-} can be used as a prefix for a control character, as in
! @samp{\C-s} for ASCII control-S, and @samp{\M-} can be used as a prefix for
  a Meta character, as in @samp{\M-a} for @kbd{Meta-A} or @samp{\M-\C-a} for
  @address@hidden
  
  @cindex international characters in @file{.emacs}
! @cindex non-ASCII characters in @file{.emacs}
! If you want to include non-ASCII characters in strings in your init
  file, you should consider putting a @address@hidden:
  @var{coding-system}-*-}} tag on the first line which states the coding
  system used to save your @file{.emacs}, as explained in @ref{Recognize
! Coding}.  This is because the defaults for decoding non-ASCII text might
  not yet be set up by the time Emacs reads those parts of your init file
  which use such strings, possibly leading Emacs to decode those strings
  incorrectly.
--- 2002,2018 ----
  sequences are mandatory.
  
  @samp{\C-} can be used as a prefix for a control character, as in
! @samp{\C-s} for @acronym{ASCII} control-S, and @samp{\M-} can be used as a 
prefix for
  a Meta character, as in @samp{\M-a} for @kbd{Meta-A} or @samp{\M-\C-a} for
  @address@hidden
  
  @cindex international characters in @file{.emacs}
! @cindex address@hidden characters in @file{.emacs}
! If you want to include address@hidden characters in strings in your init
  file, you should consider putting a @address@hidden:
  @var{coding-system}-*-}} tag on the first line which states the coding
  system used to save your @file{.emacs}, as explained in @ref{Recognize
! Coding}.  This is because the defaults for decoding address@hidden text might
  not yet be set up by the time Emacs reads those parts of your init file
  which use such strings, possibly leading Emacs to decode those strings
  incorrectly.
***************
*** 2025,2031 ****
  require one and some contexts require the other.
  
  @xref{Non-ASCII Rebinding}, for information about binding commands to
! keys which send non-ASCII characters.
  
  @item True:
  @code{t} stands for `true'.
--- 2025,2031 ----
  require one and some contexts require the other.
  
  @xref{Non-ASCII Rebinding}, for information about binding commands to
! keys which send address@hidden characters.
  
  @item True:
  @code{t} stands for `true'.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]