aboutsummaryrefslogtreecommitdiffstats
path: root/src/emacs.c
diff options
context:
space:
mode:
authorDave Love <[email protected]>1999-01-24 22:37:36 +0000
committerDave Love <[email protected]>1999-01-24 22:37:36 +0000
commitc0218e1b545ea508cb5116a179906b7d010f6c8c (patch)
tree7d78c944c05ed221e70e3b205bffc78fce08cea2 /src/emacs.c
parent5b8ed07bb4eb1c1489e75ad0119d840d81bee4f0 (diff)
Comment about unibyte.
Diffstat (limited to 'src/emacs.c')
-rw-r--r--src/emacs.c6
1 files changed, 6 insertions, 0 deletions
diff --git a/src/emacs.c b/src/emacs.c
index 54e7de1a86..33d5ae290c 100644
--- a/src/emacs.c
+++ b/src/emacs.c
@@ -967,6 +967,12 @@ the Bugs section of the Emacs manual or the file BUGS.\n", argv[0]);
buffers and strings. We need to handle this before calling
init_lread, init_editfns and other places that generate Lisp strings
from text in the environment. */
+ /* Actually this shouldn't be needed as of 20.4 in a generally
+ unibyte environment. As handa says, environment values
+ aren't now decoded; also existing buffers are now made
+ unibyte during startup if .emacs sets unibyte. Tested with
+ 8-bit data in environment variables and /etc/passwd, setting
+ unibyte and Latin-1 in .emacs. -- Dave Love */
if (argmatch (argv, argc, "-unibyte", "--unibyte", 4, NULL, &skip_args)
|| argmatch (argv, argc, "-no-multibyte", "--no-multibyte", 4, NULL, &skip_args)
|| (getenv ("EMACS_UNIBYTE") && !inhibit_unibyte))