From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: emacs misbehaves without --unibyte
Date: Wed, 29 May 2002 13:11:23 +0000 (UTC) [thread overview]
Message-ID: <m17D3EZ-000IhJC@localhost> (raw)
In-Reply-To: <Pine.SUN.3.91.1020529130511.1847B-100000@is> (message from Eli Zaretskii on Wed, 29 May 2002 13:06:58 +0300 (IDT))
Eli Zaretskii <eliz@is.elta.co.il> writes:
For some reason, many systems have file-name-coding-system set to nil by
default (I never had time to find out why), which is bad mantra.
This is because nil is the default setting for
`file-name-coding-system' when for
emacs -q --no-site-file --eval '(blink-cursor-mode 0)'
from today's CVS snapshot, 2002 May 29 12:39 UTC,
GNU Emacs 21.3.50.7 (i686-pc-linux-gnu, X toolkit)
It turns out that the documentation for `file-name-coding-system' says
If it is nil, `default-file-name-coding-system' (which see) is used.
And the default value for `default-file-name-coding-system' is also
nil.
The documentation for `default-file-name-coding-system' refers back
to the documentation for `file-name-coding-system' in a circular loop.
What would be a good value to provide `default-file-name-coding-system'?
It seems odd to:
(set-language-environment 'English)
[Hmmm... in my test instance of Emacs, the preceding expression does
not change the reported value of `default-file-name-coding-system'; is
this a bug in Emacs or am I doing something wrong?]
--
Robert J. Chassell bob@rattlesnake.com
Rattlesnake Enterprises http://www.rattlesnake.com
next prev parent reply other threads:[~2002-05-29 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020529085604.GA499186@bruegel.RZ.TU-Ilmenau.DE>
2002-05-29 9:00 ` emacs misbehaves without --unibyte Eli Zaretskii
2002-05-29 9:10 ` Miles Bader
2002-05-29 10:06 ` Eli Zaretskii
2002-05-29 13:11 ` Robert J. Chassell [this message]
2002-05-29 17:02 ` Eli Zaretskii
2002-05-31 7:04 ` Richard Stallman
2002-05-30 17:04 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m17D3EZ-000IhJC@localhost \
--to=bob@rattlesnake.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).