From: Richard Stallman <rms@gnu.org>
Cc: handa@etl.go.jp, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: Setting file-name/process coding system from LANG
Date: Mon, 25 Oct 2004 09:13:46 -0400 [thread overview]
Message-ID: <E1CM4fS-00054S-71@fencepost.gnu.org> (raw)
In-Reply-To: <20041017001433.GA32553@fencepost> (message from Miles Bader on Sat, 16 Oct 2004 20:14:33 -0400)
Currently set-language-environment sets `default-file-name-coding-system',
which is overridden by `file-name-coding-system'. Startup also apparently
sets `default-file-name-coding-system' using LANG. If startup set
`file-name-coding-system' from LANG instead, then I think that would provide
the proper semantics in this case.
What do people think of this suggestion?
Which of these scenarios is more common? I'm not sure, but it doesn't
seem unreasonable to assume that _if_ LANG contains an explicit coding
system, that it's "correct".
As long as it is not hard for users to override this setting
explicitly, when they want to, I agree.
There was also the suggestion of advising users to run
set-locale-environment in order to get back to the settings
specified by the locale.
And I had this idea:
Perhaps we should add a single new language environment
named `locale' or `according-to-locale' which has the effect
of doing set-locale-environment.
Another idea is for set-language-environment to allow a language
environment name followed by a coding system name. This would appear
to the user rather similar to Handa's suggestion, but it is much
easier to implement. It would not construct a new language
environment for the combination, it would only set the language
environment and then set the coding system.
The previous discussion did not consider all of these alternatives
side by side. Could people start a new discussion doing so? Note
that the issue that was raised about how to choose the default coding
system for Chinese language environments is not really relevant here;
it is a real issue, but it is orthogonal to this one.
next prev parent reply other threads:[~2004-10-25 13:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 8:44 Setting file-name/process coding system from LANG Miles Bader
2004-10-15 0:25 ` Richard Stallman
2004-10-15 0:51 ` Miles Bader
2004-10-16 13:53 ` Richard Stallman
2004-10-17 0:14 ` Miles Bader
2004-10-25 13:13 ` Richard Stallman [this message]
2004-10-18 13:04 ` Kenichi Handa
2004-10-19 6:13 ` Richard Stallman
2004-10-19 13:13 ` Kenichi Handa
2004-10-19 13:51 ` Stefan Monnier
2004-10-20 6:02 ` Kenichi Handa
2004-10-20 10:34 ` Richard Stallman
2004-10-19 21:51 ` Miles Bader
2004-10-20 6:21 ` Kenichi Handa
2004-10-20 8:50 ` Miles Bader
2004-10-20 13:02 ` Stefan Monnier
2004-10-20 10:34 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1CM4fS-00054S-71@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@etl.go.jp \
--cc=miles@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.