diff options
| author | Richard M. Stallman | 1998-07-03 19:34:39 +0000 |
|---|---|---|
| committer | Richard M. Stallman | 1998-07-03 19:34:39 +0000 |
| commit | 430f8c73970aa2cc3ec6bd35d32337ee210279e8 (patch) | |
| tree | c9d7e074838268fa37438cb47c094a98dcf74032 | |
| parent | bca0d6075a6fc298526a7677bceaedcf180f0572 (diff) | |
| download | emacs-430f8c73970aa2cc3ec6bd35d32337ee210279e8.tar.gz emacs-430f8c73970aa2cc3ec6bd35d32337ee210279e8.zip | |
*** empty log message ***
| -rw-r--r-- | lispref/loading.texi | 2 |
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. | |||
| 317 | multibyte strings should not be noticeable, since inserting them in | 317 | multibyte strings should not be noticeable, since inserting them in |
| 318 | unibyte buffers converts them to unibyte automatically. However, if | 318 | unibyte buffers converts them to unibyte automatically. However, if |
| 319 | this does make a difference, you can force a particular Lisp file to be | 319 | this does make a difference, you can force a particular Lisp file to be |
| 320 | interpreted as unibyte by writing @samp{-*-coding: raw-text;-*-} in a | 320 | interpreted as unibyte by writing @samp{-*-unibyte: t;-*-} in a |
| 321 | comment on the file's first line. With that designator, the file will | 321 | comment on the file's first line. With that designator, the file will |
| 322 | be unconditionally be interpreted as unibyte, even in an ordinary | 322 | be unconditionally be interpreted as unibyte, even in an ordinary |
| 323 | multibyte Emacs session. | 323 | multibyte Emacs session. |