# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 899494479 0
# Node ID cbab915f61bbfe59a28c692541db95772d7eb7ce
# Parent  f72e7540940a1620e0ea2154605901eb913264a9
*** empty log message ***

diff -r f72e7540940a -r cbab915f61bb lispref/loading.texi
--- a/lispref/loading.texi	Fri Jul 03 15:15:27 1998 +0000
+++ b/lispref/loading.texi	Fri Jul 03 19:34:39 1998 +0000
@@ -317,7 +317,7 @@
 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.