[Emacs-diffs] /srv/bzr/emacs/trunk r108183: Update doc for obsolescence of "unibyte: t"

[Glenn Morris]

------------------------------------------------------------
revno: 108183
committer: Glenn Morris <address@hidden>
branch nick: trunk
timestamp: Wed 2012-05-09 19:54:07 -0700
message:
  Update doc for obsolescence of "unibyte: t"
  
  * doc/emacs/mule.texi (Disabling Multibyte):
  * doc/lispref/loading.texi (Loading Non-ASCII):
  Replace the obsolete "unibyte: t" with "coding: raw-text".
  * etc/NEWS: Related markup.
modified:
  doc/emacs/ChangeLog
  doc/emacs/mule.texi
  doc/lispref/ChangeLog
  doc/lispref/loading.texi
  etc/NEWS

=== modified file 'doc/emacs/ChangeLog'
--- a/doc/emacs/ChangeLog       2012-05-10 00:58:16 +0000
+++ b/doc/emacs/ChangeLog       2012-05-10 02:54:07 +0000
@@ -1,5 +1,8 @@
 2012-05-10  Glenn Morris  <address@hidden>
 
+       * mule.texi (Disabling Multibyte): Replace the obsolete "unibyte: t"
+       with "coding: raw-text".
+
        * files.texi (Interlocking): Mention create-lockfiles option.
 
 2012-05-09  Chong Yidong  <address@hidden>

=== modified file 'doc/emacs/mule.texi'
--- a/doc/emacs/mule.texi       2012-05-09 03:06:08 +0000
+++ b/doc/emacs/mule.texi       2012-05-10 02:54:07 +0000
@@ -287,20 +287,17 @@
 This includes the Emacs initialization
 file, @file{.emacs}, and the initialization files of packages
 such as Gnus.  However, you can specify unibyte loading for a
-particular Lisp file, by adding an entry @samp{unibyte: t} in a file
-local variables section (@pxref{File Variables}).  Then that file is
-always loaded as unibyte text.  Note that this does not represent a
-real @code{unibyte} variable, rather it just acts as an indicator
-to Emacs in the same way as @code{coding} does (@pxref{Specify Coding}).
+particular Lisp file, by adding an entry @samp{coding: raw-text} in a file
+local variables section.  @xref{Specify Coding}.
+Then that file is always loaded as unibyte text.
 @ignore
 @c I don't see the point of this statement:
 The motivation for these conventions is that it is more reliable to
 always load any particular Lisp file in the same way.
 @end ignore
-Note also that this feature only applies to @emph{loading} Lisp files
-for evaluation, not to visiting them for editing.  You can also load a
-Lisp file as unibyte, on any one occasion, by typing @kbd{C-x
address@hidden c raw-text @key{RET}} immediately before loading it.
+You can also 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.
 
 @c See http://debbugs.gnu.org/11226 for lack of unibyte tooltip.
 @vindex enable-multibyte-characters

=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2012-05-10 00:58:16 +0000
+++ b/doc/lispref/ChangeLog     2012-05-10 02:54:07 +0000
@@ -1,5 +1,8 @@
 2012-05-10  Glenn Morris  <address@hidden>
 
+       * loading.texi (Loading Non-ASCII): Replace the obsolete "unibyte: t"
+       with "coding: raw-text".
+
        * files.texi (File Locks): Mention create-lockfiles option.
 
 2012-05-09  Glenn Morris  <address@hidden>

=== modified file 'doc/lispref/loading.texi'
--- a/doc/lispref/loading.texi  2012-05-09 03:06:08 +0000
+++ b/doc/lispref/loading.texi  2012-05-10 02:54:07 +0000
@@ -374,7 +374,7 @@
 inserting them in unibyte buffers converts them to unibyte
 automatically.  However, if this does make a difference, you can force
 a particular Lisp file to be interpreted as unibyte by writing
address@hidden: t} in a local variables section.  With
address@hidden: raw-text} in a local variables section.  With
 that designator, the file will unconditionally be interpreted as
 unibyte, even in an ordinary multibyte Emacs session.  This can matter
 when making keybindings to address@hidden characters written as

=== modified file 'etc/NEWS'
--- a/etc/NEWS  2012-05-10 00:58:16 +0000
+++ b/etc/NEWS  2012-05-10 02:54:07 +0000
@@ -69,6 +69,7 @@
 ** You can prevent the creation of lock files by setting `create-lockfiles'
 to nil.  Use with caution, and only if you really need to.
 
++++
 ** Using "unibyte: t" in Lisp source files is obsolete.
 Use "coding: raw-text" instead.