[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/man/custom.texi,v
From: |
Chong Yidong |
Subject: |
[Emacs-diffs] Changes to emacs/man/custom.texi,v |
Date: |
Fri, 30 Mar 2007 23:43:16 +0000 |
CVSROOT: /sources/emacs
Module name: emacs
Changes by: Chong Yidong <cyd> 07/03/30 23:43:16
Index: custom.texi
===================================================================
RCS file: /sources/emacs/emacs/man/custom.texi,v
retrieving revision 1.127
retrieving revision 1.128
diff -u -b -r1.127 -r1.128
--- custom.texi 4 Mar 2007 18:26:37 -0000 1.127
+++ custom.texi 30 Mar 2007 23:43:16 -0000 1.128
@@ -1276,7 +1276,6 @@
* 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
@@ -1676,7 +1675,7 @@
that delimit the vector.
Language and coding systems can cause problems with key bindings
-for address@hidden characters. @xref{Non-ASCII Rebinding}.
+for address@hidden characters. @xref{Init Non-ASCII}.
@node Function Keys
@subsection Rebinding Function Keys
@@ -1817,36 +1816,6 @@
between @key{TAB} and @kbd{C-i} (and likewise for other such pairs),
because the terminal sends the same character in both cases.
address@hidden Non-ASCII Rebinding
address@hidden address@hidden Characters on the Keyboard
address@hidden rebinding address@hidden keys
address@hidden address@hidden keys, binding
-
- If your keyboard has keys that send address@hidden
-characters, such as accented letters, rebinding these keys
-must be done by using a vector like address@hidden must
-avoid the string syntax for binding
address@hidden characters, since they will be
-interpreted as meta keys. @xref{Strings of Events,,,elisp,
-The Emacs Lisp Reference Manual}.}:
-
address@hidden
-(global-set-key address@hidden 'some-function)
address@hidden example
-
address@hidden
-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 a coding system for that file that supports the
-character in question. @xref{Init Non-ASCII}.
-
- @strong{Warning:} if you change the keyboard encoding, or change
-between multibyte and unibyte mode, or anything that would alter which
-code @kbd{C-q} would insert for that character, you'll need to edit
-the Lisp expression accordingly, to use the character code generated
-by @kbd{C-q} in the new mode.
-
@node Mouse Buttons
@subsection Rebinding Mouse Buttons
@cindex mouse button events
@@ -2126,6 +2095,7 @@
* Init Examples:: How to do some things with an init file.
* Terminal Init:: Each terminal type can have an init file.
* Find Init:: How Emacs finds the init file.
+* Init Non-ASCII:: Using non-ASCII characters in an init file.
@end menu
@node Init Syntax
@@ -2176,17 +2146,8 @@
a Meta character, as in @samp{\M-a} for @kbd{Meta-A} or @samp{\M-\C-a} for
@address@hidden
address@hidden international characters in @file{.emacs}
address@hidden address@hidden characters in @file{.emacs}
address@hidden Non-ASCII}If you want to include address@hidden
-characters in strings in your init
-file, you should consider putting a @address@hidden:
address@hidden 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.
address@hidden Non-ASCII}, for information about including
address@hidden in your init file.
@item Characters:
Lisp character constant syntax consists of a @samp{?} followed by
@@ -2195,7 +2156,7 @@
strings and characters are not interchangeable in Lisp; some contexts
require one and some contexts require the other.
address@hidden Rebinding}, for information about binding commands to
address@hidden Non-ASCII}, for information about binding commands to
keys which send address@hidden characters.
@item True:
@@ -2504,6 +2465,48 @@
name in the system's data base of users.
@c LocalWords: backtab
address@hidden Init Non-ASCII
address@hidden Non-ASCII Characters in Init Files
address@hidden international characters in @file{.emacs}
address@hidden address@hidden characters in @file{.emacs}
address@hidden address@hidden keys, binding
address@hidden rebinding address@hidden keys
+
+ Language and coding systems may cause problems if your init file
+contains address@hidden characters, such as accented letters, in
+strings or key bindings.
+
+ If you want to use address@hidden characters in your init file,
+you should put a @address@hidden: @var{coding-system}-*-}} tag on
+the first line of the init file, and specify a coding system that
+supports the character(s) in question. @xref{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. You should then avoid adding Emacs Lisp code
+that modifies the coding system in other ways, such as calls to
address@hidden
+
+ To bind address@hidden keys, you must use a vector (@pxref{Init
+Rebinding}). The string syntax cannot be used, since the
address@hidden characters will be interpreted as meta keys. For
+instance:
+
address@hidden
+(global-set-key address@hidden 'some-function)
address@hidden example
+
address@hidden
+Type @kbd{C-q}, followed by the key you want to bind, to insert @var{char}.
+
+ @strong{Warning:} if you change the keyboard encoding, or change
+between multibyte and unibyte mode, or anything that would alter which
+code @kbd{C-q} would insert for that character, this keybinding may
+stop working. It is therefore advisable to use one and only one
+coding system, for your init file as well as the files you edit. For
+example, don't mix the @samp{latin-1} and @samp{latin-9} coding
+systems.
+
@ignore
arch-tag: c68abddb-4410-4fb5-925f-63394e971d93
@end ignore