GNU bug report logs - #51832
Piping unicode text in `shell-command'

Previous Next

Full log

Message #38 received at 51832 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Philipp <p.stephani2 <at> gmail.com>
Cc: 51832 <at> debbugs.gnu.org, larsi <at> gnus.org, tor.a.s.kringeland <at> ntnu.no,
 alan <at> idiocy.org
Subject: Re: bug#51832: Piping unicode text in `shell-command'
Date: Sun, 14 Nov 2021 12:56:14 +0200

> From: Philipp <p.stephani2 <at> gmail.com>
> Date: Sun, 14 Nov 2021 11:41:38 +0100
> Cc: Lars Ingebrigtsen <larsi <at> gnus.org>,
>  tor.a.s.kringeland <at> ntnu.no,
>  51832 <at> debbugs.gnu.org,
>  alan <at> idiocy.org
> 
> > I asked once why we push LANG into the environment, instead of calling
> > setlocale, which would only affect Emacs.  I don't think I saw an
> > answer to that question, or did I miss it?
> > 
> 
> AIUI the intention is that this should affect subprocesses started from Emacs.  At least that's how I interpret the comment
> 
> /* macOS doesn't set any environment variables for the locale when run
>    from the GUI. Get the locale from the OS and set LANG.  */

Why is that needed?

And if it is needed, how come we are setting LANG to an invalid locale
and the system somehow sets it to the correct locale?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.