summaryrefslogtreecommitdiff
path: root/doc/lispref/loading.texi
diff options
context:
space:
mode:
authorGlenn Morris <rgm@gnu.org>2012-05-09 19:57:10 -0700
committerGlenn Morris <rgm@gnu.org>2012-05-09 19:57:10 -0700
commit51b1e0596d4445e1f5c3fd2fa66fe597ac31d78a (patch)
tree9a5ab1b59e707f1f613cda4a5e62481656c55d4c /doc/lispref/loading.texi
parentb8a82b6930b669a8a434d685a351e52194e6f7d9 (diff)
downloademacs-51b1e0596d4445e1f5c3fd2fa66fe597ac31d78a.tar.gz
* loading.texi (Loading Non-ASCII): Multibyte sessions no longer exist.
Diffstat (limited to 'doc/lispref/loading.texi')
-rw-r--r--doc/lispref/loading.texi5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/lispref/loading.texi b/doc/lispref/loading.texi
index b012091d4a8..c585bafbdeb 100644
--- a/doc/lispref/loading.texi
+++ b/doc/lispref/loading.texi
@@ -376,9 +376,8 @@ automatically. However, if this does make a difference, you can force
a particular Lisp file to be interpreted as unibyte by writing
@samp{coding: raw-text} in a local variables section. With
that designator, the file will unconditionally be interpreted as
-unibyte, even in an ordinary multibyte Emacs session. This can matter
-when making keybindings to non-@acronym{ASCII} characters written as
-@code{?v@var{literal}}.
+unibyte. This can matter when making keybindings to
+non-@acronym{ASCII} characters written as @code{?v@var{literal}}.
@node Autoload
@section Autoload