From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, rms@gnu.org, Kenichi Handa <handa@m17n.org>
Subject: Re: Setting file-name/process coding system from LANG
Date: Wed, 20 Oct 2004 09:02:13 -0400 [thread overview]
Message-ID: <jwvzn2heejc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <buooeix93j3.fsf@mctpc71.ucom.lsi.nec.co.jp> (Miles Bader's message of "Wed, 20 Oct 2004 17:50:40 +0900")
>> And, that means that even if one changes to latin-1 lang. env.,
>> file-name-coding-system is still utf-8. Is it ok?
There is no latin-1 language, so the "latin-1 lang env" is an ill-defined
concept anyway. Thus we can make it behave any way we want.
> Yes, asking users to use set-locale-environment instead of
> set-language-environment is one way. But, I've thought that
> set-locale-environment is not a command we usually ask a
> user to use, but a function that runs at startup time. Do
> you mean to recommend users to use set-locale-environment
> always?
Yes, kind of. I'm not sure exactly what I want, but I just know that the
structure in locales (mostly the distinction between language and encoding)
is very helpful. I think we should move set-language-environment in
this direction, or make set-locale-environment easier to use interactively
and then recommend that.
Stefan
next prev parent reply other threads:[~2004-10-20 13:02 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
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 [this message]
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
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=jwvzn2heejc.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=rms@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 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).