| 1 |
Mick writes: |
| 2 |
|
| 3 |
> On Monday 02 May 2011 11:26:27 you wrote: |
| 4 |
|
| 5 |
> Thanks. Not sure if there is a difference between an env.d variable and |
| 6 |
> a profile.d variable. |
| 7 |
|
| 8 |
None you will notice, both /etc/profile.env and scripts in /etc/profile.d/ |
| 9 |
are sourced in /etc/profile. profile.env contains all stuff in /etc/env.d/ |
| 10 |
after you ran env-update. |
| 11 |
I do not manually change things in env.d, but with 'eselect editor set <n>' |
| 12 |
you can create a file /etc/env.d/99editor which will set the EDITOR variable |
| 13 |
to the editor you gave eselect as argument. Enter eselect editor list to se |
| 14 |
what's available, or just give the editor path as argument to eselect. |
| 15 |
|
| 16 |
> I've added mine to /etc/profile.d for now. I'll |
| 17 |
> see what gives when I reboot. |
| 18 |
|
| 19 |
A relogin would be enough. Or '. /etc/profile' in the shell, this is what |
| 20 |
eselects suggests to do. Or bash -l, or xterm -ls. |
| 21 |
|
| 22 |
Wonko |
Archives