195 |
characters. |
characters. |
196 |
|
|
197 |
Emacs normally loads Lisp files as multibyte, regardless of whether |
Emacs normally loads Lisp files as multibyte, regardless of whether |
198 |
you used @samp{--unibyte}. This includes the Emacs initialization |
you used @samp{--unibyte}. This includes the Emacs initialization file, |
199 |
file, @file{.emacs}, and the initialization files of Emacs packages |
@file{.emacs}, and the initialization files of Emacs packages such as |
200 |
such as Gnus. However, you can specify unibyte loading for a |
Gnus. However, you can specify unibyte loading for a particular Lisp |
201 |
particular Lisp file, by putting @w{@samp{-*-unibyte: t;-*-}} in a |
file, by putting @w{@samp{-*-unibyte: t;-*-}} in a comment on the first |
202 |
comment on the first line. Then that file is always loaded as unibyte |
line (@pxref{File Variables}). Then that file is always loaded as |
203 |
text, even if you did not start Emacs with @samp{--unibyte}. The |
unibyte text, even if you did not start Emacs with @samp{--unibyte}. |
204 |
motivation for these conventions is that it is more reliable to always |
The motivation for these conventions is that it is more reliable to |
205 |
load any particular Lisp file in the same way. However, you can load |
always load any particular Lisp file in the same way. However, you can |
206 |
a Lisp file as unibyte, on any one occasion, by typing @kbd{C-x |
load a Lisp file as unibyte, on any one occasion, by typing @kbd{C-x |
207 |
@key{RET} c raw-text @key{RET}} immediately before loading it. |
@key{RET} c raw-text @key{RET}} immediately before loading it. |
208 |
|
|
209 |
The mode line indicates whether multibyte character support is enabled |
The mode line indicates whether multibyte character support is enabled |