Re: updated list of bugs in emelfm2
- From: <tpgww@xxxxxxxxxxx>
- To: emelfm2@xxxxxxxxxxxxx
- Date: Sun, 6 Mar 2011 14:41:11 +1100
On Sat, 5 Mar 2011 01:25:21 +0300
BrainWorker BrainWorker <owl.brainworker@xxxxxxxxx> wrote:
> More complete output
>
> ==================================================
> [brainworker@brainworker-computer ~]$ echo $HOME
> /home/brainworker
>
> [brainworker@brainworker-computer ~]$ echo $XDG_CONFIG_HOME
> /home/brainworker/.config
>
> [brainworker@brainworker-computer ~]$ su
> Password:
>
> [root@brainworker-computer brainworker]# echo $HOME
> /root
>
> [root@brainworker-computer brainworker]# echo $XDG_CONFIG_HOME
> /home/brainworker/.config
>
> [root@brainworker-computer brainworker]# exit
> exit
>
> [brainworker@brainworker-computer ~]$ su -
> Password:
>
> [root@brainworker-computer ~]# echo $HOME
> /root
>
> [root@brainworker-computer ~]# echo $XDG_CONFIG_HOME
> /root/.config
> ==================================================
>
> Interesting thing for 'su'.
> Its home is /root, but config home is mine - /home/brainworker/.config
Indeed, that's the cause of the problem you've had. This has highlighted for me
that 'su'-type mechanisms can be lazy about which environment variables they
bother to update.
Regards
Tom
--
Users can unsubscribe from the list by sending email to
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by
logging into the web interface.
Other related posts:
