From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: text-quoting-style
Date: Fri, 28 Aug 2015 18:31:10 +0300 [thread overview]
Message-ID: <83zj1b2zwh.fsf@gnu.org> (raw)
In-Reply-To: <55E07794.2090707@cs.ucla.edu>
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 28 Aug 2015 08:00:36 -0700
>
> Eli Zaretskii wrote:
> > E.g., start
> > Emacs in that way in such a locale, and then look at exec-path: if
> > there are any non-ASCII file names there, I expect you to see raw
> > bytes.
>
> I'm afraid I still don't understand this sort of scenario. Any environment in
> which exec-path has unusual characters should be able to display those
> characters; if not, it's misconfigured, and programs other than Emacs will have
> trouble too.
When you set LC_ALL=C you "misconfigure" the environment. The shell
is still running in the original locale, so the calls to getenv will
bring you the original non-ASCII characters. (Or are you saying that
Posix systems will somehow convert the value of, say, PATH to adpat it
to the C locale? Windows does such things, but I thought Posix
systems don't.)
When Emacs starts, it gets the values of various coding-systems,
including the one used for DECODE_SYSTEM, from the locale's codeset.
If you set LC_ALL=C, what will you get in locale-coding-system after
startup? I don't think it will be your shell's codeset, will it?
next prev parent reply other threads:[~2015-08-28 15:31 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 2:03 text-quoting-style Stefan Monnier
2015-08-28 5:22 ` text-quoting-style David Kastrup
2015-08-28 7:06 ` text-quoting-style Paul Eggert
2015-08-28 7:37 ` text-quoting-style Eli Zaretskii
2015-08-28 7:54 ` text-quoting-style Paul Eggert
2015-08-28 8:42 ` text-quoting-style Eli Zaretskii
2015-08-28 14:39 ` text-quoting-style Yuri Khan
2015-08-28 14:49 ` text-quoting-style Eli Zaretskii
2015-08-28 15:00 ` text-quoting-style Paul Eggert
2015-08-28 15:31 ` Eli Zaretskii [this message]
2015-08-28 15:39 ` text-quoting-style Paul Eggert
2015-08-28 15:48 ` text-quoting-style Eli Zaretskii
2015-08-28 7:29 ` text-quoting-style Eli Zaretskii
2015-08-28 16:42 ` text-quoting-style Stefan Monnier
2015-08-28 17:25 ` text-quoting-style Alan Mackenzie
2015-08-28 17:48 ` text-quoting-style Paul Eggert
2015-08-28 18:28 ` text-quoting-style Alan Mackenzie
2015-08-29 14:54 ` text-quoting-style Stefan Monnier
2015-08-29 15:59 ` text-quoting-style Alan Mackenzie
2015-08-30 1:59 ` text-quoting-style Stefan Monnier
2015-08-30 13:16 ` text-quoting-style Alan Mackenzie
2015-08-31 1:30 ` text-quoting-style Stefan Monnier
2015-08-31 6:29 ` text-quoting-style Paul Eggert
2015-08-31 20:13 ` text-quoting-style Alan Mackenzie
2015-08-31 21:29 ` text-quoting-style Paul Eggert
2015-09-01 12:47 ` text-quoting-style Alan Mackenzie
2015-09-01 16:27 ` text-quoting-style Paul Eggert
2015-09-01 17:07 ` text-quoting-style David Kastrup
2015-09-01 18:35 ` text-quoting-style Alan Mackenzie
2015-09-01 23:58 ` text-quoting-style Paul Eggert
2015-09-02 9:09 ` text-quoting-style Alan Mackenzie
2015-09-02 15:13 ` text-quoting-style Paul Eggert
2015-09-01 18:44 ` text-quoting-style Eli Zaretskii
2015-09-01 19:08 ` text-quoting-style Paul Eggert
2015-09-01 13:46 ` text-quoting-style David Kastrup
2015-09-01 16:28 ` text-quoting-style Paul Eggert
2015-09-01 17:08 ` text-quoting-style David Kastrup
2015-09-01 17:34 ` text-quoting-style Paul Eggert
2015-09-01 18:30 ` text-quoting-style David Kastrup
2015-09-02 0:07 ` text-quoting-style Paul Eggert
2015-09-02 0:27 ` text-quoting-style David Kastrup
2015-09-02 15:35 ` text-quoting-style Richard Stallman
2015-08-31 20:01 ` text-quoting-style Alan Mackenzie
2015-09-01 3:31 ` text-quoting-style Stefan Monnier
2015-09-01 9:28 ` text-quoting-style Dmitry Gutov
2015-09-01 10:53 ` text-quoting-style Oleh Krehel
2015-09-01 13:03 ` text-quoting-style Alan Mackenzie
2015-09-01 16:46 ` text-quoting-style Stefan Monnier
2015-09-01 20:41 ` text-quoting-style Bastien
2015-09-01 23:47 ` text-quoting-style Paul Eggert
2015-09-02 0:18 ` text-quoting-style David Kastrup
2015-09-02 0:35 ` text-quoting-style Paul Eggert
2015-09-02 0:53 ` text-quoting-style David Kastrup
2015-09-02 6:57 ` text-quoting-style Bastien
2015-09-02 15:17 ` text-quoting-style Paul Eggert
2015-09-02 15:36 ` text-quoting-style Dmitry Gutov
2015-09-02 15:41 ` text-quoting-style Bastien Guerry
2015-09-01 22:55 ` text-quoting-style Richard Stallman
2015-09-02 9:05 ` text-quoting-style Alan Mackenzie
2015-08-31 16:10 ` text-quoting-style N. Jackson
2015-08-31 17:31 ` text-quoting-style Stefan Monnier
2015-09-02 19:34 ` text-quoting-style N. Jackson
2015-09-03 15:29 ` text-quoting-style raman
2015-08-31 6:15 ` text-quoting-style Paul Eggert
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=83zj1b2zwh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).