unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Gottfried <gottfried@posteo.de>
To: help-guix@gnu.org
Subject: Fwd: export LC_ALL=C
Date: Wed, 26 Oct 2022 18:32:24 +0000	[thread overview]
Message-ID: <6751b005-d959-7899-3920-0297ac66847a@posteo.de> (raw)
In-Reply-To: <602dcf6d-af9b-f804-71b9-a97ee939a7d2@posteo.de>


[-- Attachment #1.1.1: Type: text/plain, Size: 2076 bytes --]

sincere thanks
Gottfried

a good explanation is always useful, also for others who will look in 
the history.


Am 24.10.22 um 14:40 schrieb Tobias Geerinckx-Rice:
> Hi Gottfried,
> 
> I hope this strikes the right balance between explaining ‘environment 
> variables’ from scratch and answering your immediate question.
> 
> Gottfried 写道:
>> 1.  Will this now overwrite my variables for ever, or only for some time?
> 
> Environment variables are not saved.  They can be *set* by configuration 
> files, such at /etc/profile, but these files are not updated when you 
> type ‘export GUIX=awesome’ on the command line.
> 
> Setting LC_ALL like this affects your current shell, and it will be 
> inherited by child processes (hence why the ‘guix’ child will speak 
> English after setting LC_ALL=C in the parent shell), but they exist 
> purely in RAM for the lifetime of each process.
> 
> The also do not propagate to ancestor or sibling processes: setting 
> LC_ALL in one terminal window has no effect on any other windows.  Nor 
> will setting LC_ALL in a shell affect new processes you launch 
> elsewhere, such as from your desktop menu.  Only child processes 
> launched in the same shell/window will inherit it.
> 
> As soon as you close that terminal, type ‘exit’ in the (guix) shell, or 
> trip over your power cable, the setting is gone.
> 
>> 2.  How can I set it back to my original state?
> 
> Environment variables have no built-in notion of history, or defaults.  
> They are just variables, and setting them to something new overwrites 
> the old value (if any).
> 
> So:
> 
> ~$ echo $LC_ALL        # yours will be de_DE, I presume
> en_IE.utf8
> ~$ LC_OLD=$LC_ALL    # save the old value
> ~$ export LC_ALL=C    # in with the new
> ~$ echo $LC_ALL        # do the thing
> C
> ~$ LC_ALL=$LC_OLD    # restore the old value
> 
> But really, in practice, I'd just close the window/shell once done…  
> they are so cheap.
> 
> Kind regards,
> 
> T G-R


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3193 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

           reply	other threads:[~2022-10-26 18:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <602dcf6d-af9b-f804-71b9-a97ee939a7d2@posteo.de>]

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=6751b005-d959-7899-3920-0297ac66847a@posteo.de \
    --to=gottfried@posteo.de \
    --cc=help-guix@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.
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).