Mercurial > emacs

comparison man/mule.texi @ 58624:a322009ca3d0

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
* custom.texi (File Variables): Add `unibyte' and make it more clear that `unibyte' and `coding' are special. Suggested by Simon Krahnke <overlord@gmx.li>. * mule.texi (Enabling Multibyte): Refer to File Variables. Suggested by Simon Krahnke <overlord@gmx.li>.
author Reiner Steib <Reiner.Steib@gmx.de>
date Mon, 29 Nov 2004 15:58:15 +0000
parents 7232ffdd33dd
children 48aa868cde0b f2ebccfa87d4
comparison
equal deleted inserted replaced
58623:834b3aeb850f 58624:a322009ca3d0
193 initialization from the values of environment variables, 193 initialization from the values of environment variables,
194 @file{/etc/passwd} entries etc.@: that contain non-@acronym{ASCII} 8-bit 194 @file{/etc/passwd} entries etc.@: that contain non-@acronym{ASCII} 8-bit
195 characters. 195 characters.
196 196
197 Emacs normally loads Lisp files as multibyte, regardless of whether 197 Emacs normally loads Lisp files as multibyte, regardless of whether
198 you used @samp{--unibyte}. This includes the Emacs initialization 198 you used @samp{--unibyte}. This includes the Emacs initialization file,
199 file, @file{.emacs}, and the initialization files of Emacs packages 199 @file{.emacs}, and the initialization files of Emacs packages such as
200 such as Gnus. However, you can specify unibyte loading for a 200 Gnus. However, you can specify unibyte loading for a particular Lisp
201 particular Lisp file, by putting @w{@samp{-*-unibyte: t;-*-}} in a 201 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 202 line (@pxref{File Variables}). Then that file is always loaded as
203 text, even if you did not start Emacs with @samp{--unibyte}. The 203 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 204 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 205 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 206 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. 207 @key{RET} c raw-text @key{RET}} immediately before loading it.
208 208
209 The mode line indicates whether multibyte character support is enabled 209 The mode line indicates whether multibyte character support is enabled
210 in the current buffer. If it is, there are two or more characters (most 210 in the current buffer. If it is, there are two or more characters (most
211 often two dashes) before the colon near the beginning of the mode line. 211 often two dashes) before the colon near the beginning of the mode line.