On 28Mar2006 21:01, Michelle Konzack <[EMAIL PROTECTED]> wrote: | on the Mailinglist <debian-user-german> was one person which told me, | that this BUG is known in Debian/Sarge. However, I have found no infos.
Ouch. | If xterm is called with | | Exec xterm -e program | | then some environements variables are lost, even if you try | | Exec xterm -e /bin/bash -c program Naturally. The vars will be lost here because "/bin/bash" is a program, so the vars are lost to it already and it does nothing to restore them. | The solution is to call the program with a login shell | Exec xterm -e /bin/bash -l -c program This is kind of nasty. Rerunning the entire login environment setup can be very slow on many systems. New shells and terminals should be fast, ideally. | or use "env" like | Exec xterm -e env "TMPDIR=$TEMPDIR" program | last looks a little bit stupid to me... No, it is better than the login shell approach because it adjusts _only_ the variable of interest. The login will redo many many variables, possibly damaging any special setup you have done since your login. Alternatively, if you have established that the environment is ok inside FVWM and broken in the xterm, use a different terminal emulator. I am using rxvt-unicode quite happily (command name is "urxvt"). Cheers, -- Cameron Simpson <[EMAIL PROTECTED]> DoD#743 http://www.cskk.ezoshosting.com/cs/ Tsuka O Hanasu To Iu Koto ('Letting Go the Hilt'). 'Letting go the hilt' has several meanings. It means winning without a sword. Also, it has the meaning of being unable to win although carrying a long sword. I cannot record all the various shades of meaning. One must practice diligently. - Musashi
