diff options
| author | Chong Yidong <cyd@stupidchicken.com> | 2010-08-22 17:15:20 -0400 |
|---|---|---|
| committer | Chong Yidong <cyd@stupidchicken.com> | 2010-08-22 17:15:20 -0400 |
| commit | 198a7a97ff99b96523f7c0736aa303d305595094 (patch) | |
| tree | 956fc21f7bd577ca58c981dd67859409dfb0153e /doc/lispref/loading.texi | |
| parent | b0126eac41487b9bca5af5cbb2212ff5b2c58b80 (diff) | |
| download | emacs-198a7a97ff99b96523f7c0736aa303d305595094.tar.gz | |
Make obsolete --unibyte argument do nothing (Bug#6886).
* src/emacs.c (main): Remove --unibyte handling (Bug#6886).
* lisp/startup.el (command-line-1): Issue warning for ignored arguments
--unibyte, etc (Bug#6886).
* doc/lispref/nonascii.texi (Text Representations):
* doc/lispref/loading.texi (Loading Non-ASCII):
* doc/lispref/compile.texi (Byte Compilation): Don't mention obsolete
--unibyte command-line argument.
Diffstat (limited to 'doc/lispref/loading.texi')
| -rw-r--r-- | doc/lispref/loading.texi | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/doc/lispref/loading.texi b/doc/lispref/loading.texi index bbdd67fc3a5..dee2a0252eb 100644 --- a/doc/lispref/loading.texi +++ b/doc/lispref/loading.texi @@ -367,13 +367,6 @@ example) is read without decoding, the text of the program will be unibyte text, and its string constants will be unibyte strings. @xref{Coding Systems}. - To make the results more predictable, Emacs always performs decoding -into the multibyte representation when loading Lisp files, even if it -was started with the @samp{--unibyte} option. This means that string -constants with non-@acronym{ASCII} characters translate into multibyte -strings. The only exception is when a particular file specifies no -decoding. - The reason Emacs is designed this way is so that Lisp programs give predictable results, regardless of how Emacs was started. In addition, this enables programs that depend on using multibyte text to work even |