On Tue, Nov 19, 2002 at 11:30:45PM -0500, Dan Espen wrote:
> Norvell Spearman <norvell_at_houseofspearman.org> 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.
Pardon my ignorance, but I still don't quite understand. How is the
``for i in'' part relative to $HOME when the error message says:
[FVWM][Read]: <<ERROR>> file 'Menu/*.men' not found in \
/home/norvell/.fvwm or /usr/share/fvwm
Doesn't that suggest that fvwm starts looking in $HOME/.fvwm for i (but
doesn't see it), then in /usr/share/fvwm, before looking in $HOME?
> I think you'll find full paths work better.
That's what I'll end up doing. I'll eventually change the script
commands to look in /usr/share/fvwm, then in $FVWM_USERDIR. I'm working
on a klugey approach to menu configuration: one file per app, each
file containing both menu entry and style commands. Thanks for your
help and for responding so quickly.
--
Norvell Spearman
--
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 majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Nov 19 2002 - 22:12:44 GMT