From: Gottfried <gottfried@posteo.de>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: help-guix@gnu.org
Subject: Re: export LC_ALL=C
Date: Wed, 26 Oct 2022 18:31:19 +0000 [thread overview]
Message-ID: <04e292bd-5698-8d48-a488-79ae3452f146@posteo.de> (raw)
In-Reply-To: <DVAmL-JuPf7q_2gOdabjCd0NBnf6kFF_c6MX8RhyVr9KmXwh-uUz4dKAokeN-aYUvLUpeRFsW347ikf3DOomYJIgjUQvLcJ_LqmwHXC4134=@protonmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1053 bytes --]
sincere thanks
Gottfried
Am 24.10.22 um 15:19 schrieb Luis Felipe:
> Hi Gottfried,
>
>
> ------- Original Message -------
> On Monday, October 24th, 2022 at 12:17, Gottfried <gottfried@posteo.de> wrote:
>
>
> What I do is set the LANG variable to C. For example, in a terminal, you'd run:
>
> LANG=C guix describe
>
> And you'd get the output in English only for that command. If you run it again without the "LANG=C" part, you should see the output in German.
>
> I see the value C as "the language or locale in which programs were originally written". In this case it is English because Guix is written in English.
>
> You can use the same trick to use programs in any of the languages they are localized to. For example, the following prints the output in French:
>
> LANG=fr_FR.utf8 guix describe
>
> To find out what kind of values you can pass to LANG, you can run the following command:
>
> locale --all
>
> That command is provided by the package "gcc-toolchain".
>
> Hope that helps,
>
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-10-26 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 12:17 export LC_ALL=C Gottfried
2022-10-24 12:40 ` Tobias Geerinckx-Rice
2022-10-24 12:50 ` Tobias Geerinckx-Rice
2022-10-24 13:19 ` Luis Felipe
2022-10-24 14:33 ` Felix Lechner via
2022-10-26 18:31 ` Gottfried [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-25 5:22 Nathan Dehnel
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=04e292bd-5698-8d48-a488-79ae3452f146@posteo.de \
--to=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=luis.felipe.la@protonmail.com \
/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.
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).