[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fvwm
Subject:    Re: FVWM: $PATH in Test x
From:       Dominique Michel <dominique.michel () vtxnet ! ch>
Date:       2012-05-02 22:04:16
Message-ID: 20120503000416.7c44f9a3 () tuxstudio
[Download RAW message or body]

Le Tue, 1 May 2012 21:28:48 +0100,
Thomas Adam <thomas@fvwm.org> a écrit :

> On 1 May 2012 20:46, Jaimos F Skriletz
> <jaimos@diamond.boisestate.edu> wrote:
> > On 05/01/2012 12:53 PM, Dominique Michel wrote:
> >>
> >> A very common way to write $HOME in a path is with ~
> >>
> >> With "PATH="~/bin:$PATH" into ~/.bash_profile, I get only the first
> >> menu line on the screen.
> >> With "PATH="/home/dom/bin:$PATH" into ~/.bash_profile, I get the 2
> >> menu lines on the screen.
> >>
> >> It look like the "Test (x xdradio) ..." work only in the first
> >> case. Is it a bug in fvwm or somewhere else, or some obscure and
> >> wanted stuff I am not aware of?
> >
> > It is an issue with the shell, and how it expands special
> > characters. When the shell encounters an Env Variable or a special
> > character like ~, *, !, etc it exapnds it based on the rules of the
> > character.
> 
> Not for the Test command, it isn't.  This doesn't have anything to do
> with the shell or the quoting problems you'd find there.  And
> actually, this is inherent in the environment FVWM is using for
> itself, not in ~/.bash_profile, which unless sourced before FVWM
> starts, might not have the same PATH set as interactive shells.

On gentoo, ~/.bash_profile is sourced one time at login and $PATH is
the same than for the interactive shells (if it is not defined
differently into ~/.bashrc for the laters). After the login, I start
fvwm with startx. So, it is sourced before fvwm starts, and as Jaimos
pointed out, the ~ is not expanded by the shell.

Anyway, I will stop to use ~ in my config and use $HOME instead.

Thanks,
Dominique

[prev in list] [next in list] [prev in thread] [next in thread]