procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* custom.texi (File Variables): Add `unibyte' and make it more

Browse source 
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>.
This commit is contained in:
Reiner Steib 2004-11-29 15:58:15 +00:00
parent 2ec7f67a91
commit 2e66e5b785
3 changed files with 27 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
man/ChangeLog
View file

@ -1,3 +1,12 @@
2004-11-29 Reiner Steib <Reiner.Steib@gmx.de>
* 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>.
2004-11-26 Jan Dj,Ad(Brv <jan.h.d@swipnet.se> 2004-11-26 Jan Dj,Ad(Brv <jan.h.d@swipnet.se>
* frames.texi (Dialog Boxes): Rename use-old-gtk-file-dialog to * frames.texi (Dialog Boxes): Rename use-old-gtk-file-dialog to

16
man/custom.texi
View file

@ -961,7 +961,8 @@ numeric values:
You can also specify the coding system for a file in this way: just You can also specify the coding system for a file in this way: just
specify a value for the ``variable'' named @code{coding}. The ``value'' specify a value for the ``variable'' named @code{coding}. The ``value''
must be a coding system name that Emacs recognizes. @xref{Coding must be a coding system name that Emacs recognizes. @xref{Coding
Systems}. Systems}. @w{@samp{unibyte: t}} specifies unibyte loading for a
particular Lisp file. @xref{Enabling Multibyte}.
The @code{eval} pseudo-variable, described below, can be specified in The @code{eval} pseudo-variable, described below, can be specified in
the first line as well. the first line as well.
@ -1022,14 +1023,15 @@ Here's an example of doing this:
# End: # End:
@end example @end example
Two ``variable names'' have special meanings in a local variables Some ``variable names'' have special meanings in a local variables
list: a value for the variable @code{mode} really sets the major mode, list: a value for the variable @code{mode} really sets the major mode,
and a value for the variable @code{eval} is simply evaluated as an and a value for the variable @code{eval} is simply evaluated as an
expression and the value is ignored. @code{mode} and @code{eval} are expression and the value is ignored. @code{coding}, @code{unibyte},
not real variables; setting variables named @code{mode} and @code{eval} @code{mode} and @code{eval} are not real variables; setting variables
in any other context has no special meaning. @emph{If @code{mode} is named @code{coding}, @code{unibyte}, @code{mode} and @code{eval} in any
used to set a major mode, it should be the first ``variable'' in the other context has no special meaning. @emph{If @code{mode} is used to
list.} Otherwise, the entries that precede it in the list of the local set a major mode, it should be the first ``variable'' in the list.}
Otherwise, the entries that precede it in the list of the local
variables are likely to be ignored, since most modes kill all local variables are likely to be ignored, since most modes kill all local
variables as part of their initialization. variables as part of their initialization.

18
man/mule.texi
View file

@ -195,15 +195,15 @@ initialization from the values of environment variables,
characters. characters.
Emacs normally loads Lisp files as multibyte, regardless of whether Emacs normally loads Lisp files as multibyte, regardless of whether
you used @samp{--unibyte}. This includes the Emacs initialization you used @samp{--unibyte}. This includes the Emacs initialization file,
file, @file{.emacs}, and the initialization files of Emacs packages @file{.emacs}, and the initialization files of Emacs packages such as
such as Gnus. However, you can specify unibyte loading for a Gnus. However, you can specify unibyte loading for a particular Lisp
particular Lisp file, by putting @w{@samp{-*-unibyte: t;-*-}} in a file, by putting @w{@samp{-*-unibyte: t;-*-}} in a comment on the first
comment on the first line. Then that file is always loaded as unibyte line (@pxref{File Variables}). Then that file is always loaded as
text, even if you did not start Emacs with @samp{--unibyte}. The unibyte text, even if you did not start Emacs with @samp{--unibyte}.
motivation for these conventions is that it is more reliable to always The motivation for these conventions is that it is more reliable to
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
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
@key{RET} c raw-text @key{RET}} immediately before loading it. @key{RET} c raw-text @key{RET}} immediately before loading it.
The mode line indicates whether multibyte character support is enabled The mode line indicates whether multibyte character support is enabled