From: Reiner Steib Date: Mon, 29 Nov 2004 15:58:15 +0000 (+0000) Subject: * custom.texi (File Variables): Add `unibyte' and make it more X-Git-Tag: ttn-vms-21-2-B4~3567 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=2e66e5b785082ca0a50d4b03486ddb3e957153e6;p=emacs.git * custom.texi (File Variables): Add `unibyte' and make it more clear that `unibyte' and `coding' are special. Suggested by Simon Krahnke . * mule.texi (Enabling Multibyte): Refer to File Variables. Suggested by Simon Krahnke . --- diff --git a/man/ChangeLog b/man/ChangeLog index 9b620deb734..c8a9edc8f27 100644 --- a/man/ChangeLog +++ b/man/ChangeLog @@ -1,3 +1,12 @@ +2004-11-29 Reiner Steib + + * custom.texi (File Variables): Add `unibyte' and make it more + clear that `unibyte' and `coding' are special. Suggested by Simon + Krahnke . + + * mule.texi (Enabling Multibyte): Refer to File Variables. + Suggested by Simon Krahnke . + 2004-11-26 Jan Dj,Ad(Brv * frames.texi (Dialog Boxes): Rename use-old-gtk-file-dialog to diff --git a/man/custom.texi b/man/custom.texi index 3065ad3de23..6823dc3bfe5 100644 --- a/man/custom.texi +++ b/man/custom.texi @@ -961,7 +961,8 @@ numeric values: 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'' 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 first line as well. @@ -1022,14 +1023,15 @@ Here's an example of doing this: # End: @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, 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 -not real variables; setting variables named @code{mode} and @code{eval} -in any other context has no special meaning. @emph{If @code{mode} is -used to 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 +expression and the value is ignored. @code{coding}, @code{unibyte}, +@code{mode} and @code{eval} are not real variables; setting variables +named @code{coding}, @code{unibyte}, @code{mode} and @code{eval} in any +other context has no special meaning. @emph{If @code{mode} is used to +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 as part of their initialization. diff --git a/man/mule.texi b/man/mule.texi index 86349c0b40e..4bc6b9939dd 100644 --- a/man/mule.texi +++ b/man/mule.texi @@ -195,15 +195,15 @@ initialization from the values of environment variables, characters. Emacs normally loads Lisp files as multibyte, regardless of whether -you used @samp{--unibyte}. This includes the Emacs initialization -file, @file{.emacs}, and the initialization files of Emacs packages -such as Gnus. However, you can specify unibyte loading for a -particular Lisp file, by putting @w{@samp{-*-unibyte: t;-*-}} in a -comment on the first line. Then that file is always loaded as unibyte -text, even if you did not start Emacs with @samp{--unibyte}. The -motivation for these conventions is that it is more reliable to always -load any particular Lisp file in the same way. However, you can load -a Lisp file as unibyte, on any one occasion, by typing @kbd{C-x +you used @samp{--unibyte}. This includes the Emacs initialization file, +@file{.emacs}, and the initialization files of Emacs packages such as +Gnus. However, you can specify unibyte loading for a particular Lisp +file, by putting @w{@samp{-*-unibyte: t;-*-}} in a comment on the first +line (@pxref{File Variables}). Then that file is always loaded as +unibyte text, even if you did not start Emacs with @samp{--unibyte}. +The motivation for these conventions is that it is more reliable to +always load any particular Lisp file in the same way. However, you can +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. The mode line indicates whether multibyte character support is enabled