Re: FVWM: PipeRead problem

From: Dan Espen <dane_at_mk.telcordia.com>
Date: Wed, 20 Nov 2002 00:42:56 -0500

Norvell Spearman <norvell_at_houseofspearman.org> writes:
> 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

You still see the "*" in the file name because the shell didn't
expand Menu/*.man since no file matched.

Go to $HOME/.fvwm and type in:

ls 'Menu/*.man'

I hope I'm explaining this right, its getting late.

-- 
Dan Espen                           E-mail: dane_at_mk.telcordia.com
--
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:45:14 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:54 BST