Norvell Spearman <[EMAIL PROTECTED]> writes: > fvwm-2.5.4 > > I have the following line in a configuration file > > PipeRead 'for i in Menu/*.men; do echo read $i; done'
The for i in part is relative to $HOME. The fvwm read command reads in $HOME/.fvwm. If you change the first part to .fvwm/Menu/*.man it will screw up $i for the read. > which produces the following error message in my ~/.xsession-errors: > > [FVWM][Read]: <<ERROR>> file 'Menu/*.men' not found in \ > /home/norvell/.fvwm or /usr/share/fvwm > > Yet there is a directory in my .fvwm directory named Menu in which are > files with men as the extension. If I change the PipeRead command to: > > PipeRead 'for i in $HOME/.fvwm/Menu/*.men; do echo read $i; done' > > fvwm does what I need it to. What's wrong with my first PipeRead? > Thanks for any answers. I think you'll find full paths work better. Another way to refer to "$HOME/.fvwm" is $FVWM_USERDIR. -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
