I had contemplated the same thing, but when you say
'what_ever_shell_you_are_using_profile'
how do you deal with the fact that shell syntax for dealing
with the environment varies - for exmaple:
export FOO=moo
for ksh and
setenv FOO moo
for csh
The only universal solution I could come up with would be to have
the various login agents (login/xdm/sshd...) check for and
act on $HOME/.environment before the desired shell is invoked.
Perhaps something could go into the PAM session management to
look after it...
Regards,
DigbyT
On Tue, Feb 07, 2006 at 10:09:44AM +0200, Muurim?ki Perttu wrote:
> And from here we can clearly see the answer ;)
>
> .environment -file in ${HOME} which is sourced by .xsession AND
> .bash_profile AND .what_ever_shell_you_are_using_profile . Probably
> you can make your GNOME/KDE startup-systems to source it too but I'm
> using neither so I don't know for sure.
>
> .bashrc is reserved for only bash-spesific stuff as aliases, functions
> and so forth. .bash_profile icludes only two lines:
>
> source ${HOME}/.environment
> source ${HOME}/.bashrc
>
> .environment is (or at least my .environment is) basically list of
> environment-variables and this approach has worked very well for me :)
> Now even Emacs (started under X) knows about my HTTP_PROXY and PATH!
>
> --
>
> Perttu Muurim?ki
> Suunnittelija
> Tietopalveluyksikk?
> Tilastokeskus
> s?hk?posti: [EMAIL PROTECTED]
> puh. (09) 1734 3236
--
Digby R. S. Tarvin digbyt(at)digbyt.com
http://www.digbyt.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
