On 00:42 20 Nov 2002, Dan Espen <dane_at_mk.telcordia.com> wrote:
| 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'
[...]
| > [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. [...]
| I hope I'm explaining this right, its getting late.
Sound right to me. Assuming the code is actually running where he hopes
(i.e. $HOME is fine), the above line might be modified thus:
PipeRead 'for i in Menu/*.men; do [ -f $i ] && echo read $i; done'
or just thus:
PipeRead 'ls -d Menu/*.men 2>/dev/null | sed "s/^/read /"'
Your call as to which is easier to read :-)
Cheers,
--
Cameron Simpson, DoD#743 cs_at_zip.com.au http://www.zip.com.au/~cs/
You can fool too many of the people too much of the time. - James Thurber
--
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 Wed Nov 20 2002 - 01:36:46 GMT