| 1 |
Mick writes: |
| 2 |
|
| 3 |
> On Saturday 26 June 2010 11:40:14 Mick wrote: |
| 4 |
|
| 5 |
> > I have not exported any locale in my ~/.bashrc, so should a plain |
| 6 |
> > user locale reflect what's in /etc/env.d/02locale? |
| 7 |
> > |
| 8 |
> > I added /etc/env.d/02locale as you show above, but my plain user |
| 9 |
> > still shows all settings as "en_US.UTF-8" ... where is this US |
| 10 |
> > setting read from? |
| 11 |
> |
| 12 |
> Oops! This is more complicated that I thought ... |
| 13 |
> |
| 14 |
> If, always as a plain user, I use aterm then /etc/env.d/02locale is |
| 15 |
> read and LANG is en_GB.UTF-8. However, if I use xterm it is still |
| 16 |
> LANG=en_US.UTF-8 |
| 17 |
|
| 18 |
Your aterm is configured as a login shell, and as such reads /etc/profile, |
| 19 |
which reads /etc/profile.env (and ~/.[bash]profile). xterm is not a login |
| 20 |
shell, and reads /etc/bash/bashrc (and ~/.bashrc). You can call xterm with |
| 21 |
the -ls option to make it alogin shell. For konsole, I have set it to |
| 22 |
execute bash -l to make it a login shell. |
| 23 |
|
| 24 |
Another workaround might be to read /etc/profile.env in your .bashrc, or |
| 25 |
in /etc/bash/bashrc. |
| 26 |
|
| 27 |
Wonko |
Archives