aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDave Love2000-07-27 13:11:10 +0000
committerDave Love2000-07-27 13:11:10 +0000
commit6824708b09e5e8aa1f0d440ef5c5dcf506606a7d (patch)
tree3abef41176a63be00131aa1824fc36775f37e4a6
parent315fe0e9538ddb1f03c46dad7e87dab922b891ac (diff)
downloademacs-6824708b09e5e8aa1f0d440ef5c5dcf506606a7d.tar.gz
emacs-6824708b09e5e8aa1f0d440ef5c5dcf506606a7d.zip
Mention keybindings of non-ASCII chars.
-rw-r--r--lispref/loading.texi3
1 files changed, 2 insertions, 1 deletions
diff --git a/lispref/loading.texi b/lispref/loading.texi
index c53edbe77ec..efc1d991fbe 100644
--- a/lispref/loading.texi
+++ b/lispref/loading.texi
@@ -322,7 +322,8 @@ this does make a difference, you can force a particular Lisp file to be
322interpreted as unibyte by writing @samp{-*-unibyte: t;-*-} in a 322interpreted as unibyte by writing @samp{-*-unibyte: t;-*-} in a
323comment on the file's first line. With that designator, the file will 323comment on the file's first line. With that designator, the file will
324unconditionally be interpreted as unibyte, even in an ordinary 324unconditionally be interpreted as unibyte, even in an ordinary
325multibyte Emacs session. 325multibyte Emacs session. This can matter when making keybindings to
326non-@sc{ascii} characters written as @code{?v@var{literal}}.
326 327
327@node Autoload 328@node Autoload
328@section Autoload 329@section Autoload