summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>1998-07-03 19:34:39 +0000
committerRichard M. Stallman <rms@gnu.org>1998-07-03 19:34:39 +0000
commit430f8c73970aa2cc3ec6bd35d32337ee210279e8 (patch)
treec9d7e074838268fa37438cb47c094a98dcf74032
parentbca0d6075a6fc298526a7677bceaedcf180f0572 (diff)
downloademacs-430f8c73970aa2cc3ec6bd35d32337ee210279e8.tar.gz
emacs-430f8c73970aa2cc3ec6bd35d32337ee210279e8.tar.bz2
emacs-430f8c73970aa2cc3ec6bd35d32337ee210279e8.zip
*** empty log message ***
-rw-r--r--lispref/loading.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/lispref/loading.texi b/lispref/loading.texi
index 093644354e7..8613442192a 100644
--- a/lispref/loading.texi
+++ b/lispref/loading.texi
@@ -317,7 +317,7 @@ appropriately.
multibyte strings should not be noticeable, since inserting them in
unibyte buffers converts them to unibyte 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
+interpreted as unibyte by writing @samp{-*-unibyte: t;-*-} in a
comment on the file's first line. With that designator, the file will
be unconditionally be interpreted as unibyte, even in an ordinary
multibyte Emacs session.