unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22392@debbugs.gnu.org, Anders Lindgren <andlind@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Emacs OS X GUI doesn't set locale
Date: Tue, 26 Jan 2016 23:05:29 +0000	[thread overview]
Message-ID: <m2bn880wna.fsf@galloway.idiocy.org> (raw)
In-Reply-To: <83lh7c1igo.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 26 Jan 2016 17:14:15 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Yes, that is why I asked if he had considered that approach. The reason I asked
>> was if there was any advantage in setting the LANG variable of the Emacs
>> process itself, or if this only was of interest of subprocesses.
>
> Passing our LANG to subprocesses would be a bad idea, I think.  Emacs
> is not supposed to change the environment of the child processes just
> because it needs that for itself.

To my mind it might be a plus for Emacs to pass it's LANG along in this
particular situation as UNIX style sub-processes aren't going to pick up
the correct locale themselves and so will, presumably, default to "C",
no matter what the locale should be.

eg. running the locale command from within Emacs:

LANG=
LC_COLLATE="C"
LC_CTYPE="C"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL=

vs running it from terminal.app:

LANG="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_CTYPE="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_ALL=

-- 
Alan Third



  parent reply	other threads:[~2016-01-26 23:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 22:18 Emacs OS X GUI doesn't set locale Alan Third
2016-01-26  7:11 ` Anders Lindgren
2016-01-26 14:44   ` Eli Zaretskii
2016-01-26 15:06     ` Anders Lindgren
2016-01-26 15:14       ` Eli Zaretskii
2016-01-26 16:58         ` Anders Lindgren
2016-01-26 23:05         ` Alan Third [this message]
2016-01-27 18:06           ` Paul Eggert
2016-01-27 19:44             ` Eli Zaretskii
2016-01-27 22:27               ` Paul Eggert
2016-01-28 22:53             ` Alan Third
2016-02-01  5:03               ` Anders Lindgren
2016-02-01 17:48                 ` bug#22392: " Alan Third
2016-02-01 18:57                 ` Eli Zaretskii
2016-01-26 22:50   ` Alan Third
2016-01-27  6:21     ` Anders Lindgren
2016-01-27 15:53       ` Eli Zaretskii

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=m2bn880wna.fsf@galloway.idiocy.org \
    --to=alan@idiocy.org \
    --cc=22392@debbugs.gnu.org \
    --cc=andlind@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).