On 05Dec13 11:00 +0100, lee wrote: > | PipeRead 'for i in /bin/ls $HOME/.fvwm/*.fvwm; do echo Read $i; done' > > which seemed to read the contents of an executable file and tried to > execute whatever it read as commands. That appears to be way too > dangerous to use.
It reads /bin/ls as input file. Try: PipeRead 'for i in $HOME/.fvwm/*.fvwm; do echo Read $i; done' If you need alphabetical order try: PipeRead 'for i in $(echo $HOME/.fvwm/*.fvwm | sort) ; do echo Read $i; done' I used a similar setup, but I discovered, that the order of inclusion is not arbitrary, because of function definitions and other config stuff. A handy solution for configuration directories contains files with number-prefixed names like 00-main.conf 01-variables.conf 02-functions.conf ... Cheers,
