On Wed, Mar 26, 2025 at 13:09:45 +0100, Léa Gris wrote: > $ LC_ALL=C locale > LANG=fr_FR.UTF-8 > LANGUAGE=fr_FR:fr_CA:en > LC_CTYPE="C" > LC_NUMERIC="C" > LC_TIME="C" > LC_COLLATE="C" > LC_MONETARY="C" > LC_MESSAGES="C" > LC_PAPER="C" > LC_NAME="C" > LC_ADDRESS="C" > LC_TELEPHONE="C" > LC_MEASUREMENT="C" > LC_IDENTIFICATION="C" > LC_ALL=C > > > I wonder if locale is switched accordingly to environment variables, but > environment variables may not automatically switch to the new locale.
You're operating under a misconception here. Setting LC_ALL does *not* change the settings of the other variables. It just overrides them. hobbit:~$ env | grep -e LANG -e LC_ LANG=en_US.utf8 LC_TIME=C hobbit:~$ LC_ALL=POSIX env | grep -e LANG -e LC_ LC_ALL=POSIX LANG=en_US.utf8 LC_TIME=C When I add an LC_ALL definition in the second command, it doesn't change the other two. It just adds a third variable. The output of locale is reporting the *effective* settings (inherited or implied) in addition to the *explicit* variable settings. The way you can tell the difference is by the double quotes. hobbit:~$ env | grep -e LANG -e LC_ LANG=en_US.utf8 LC_TIME=C hobbit:~$ locale LANG=en_US.utf8 LANGUAGE= LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME=C LC_COLLATE="en_US.utf8" LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL= In my case, LC_TIME is explicitly set, so it does *not* have double quotes around its value in the output of locale. But variables like LC_COLLATE are not explicitly set, so locale shows me what value is being used, but it puts double quotes around it to say that this is an implied value, not an explictly set variable.
