Stuart Longland writes:
> On 05/12/13 20:45, bastian-fvwm-org-20121...@t6l.de wrote:
>>
>> If you need alphabetical order try:
>> PipeRead 'for i in $(echo $HOME/.fvwm/*.fvwm | sort) ; do echo Read $i; done'
>
> Or even:
> PipeRead `ls -1 $HOME/.fvwm/*.fvwm | while read i; do echo Read $i; done`
bastian-fvwm-org-20121...@t6l.de writes:
> 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
On 05/12/13 20:45, bastian-fvwm-org-20121...@t6l.de wrote:
>
> If you need alphabetical order try:
> PipeRead 'for i in $(echo $HOME/.fvwm/*.fvwm | sort) ; do echo Read $i; done'
Or even:
PipeRead `ls -1 $HOME/.fvwm/*.fvwm | while read i; do echo Read $i; done`
More than one way to skin this cat
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 f
Hi,
what would be the best way to read configuration file snippets from a
directory or from various directories?
Currently I have ~/.fvwm/.fvwm2rc to start with and statements in it
like
,
| [...]
| Read fvwm-colours.fvwm
| Read fvwm-desks.fvwm
| Read fvwm-menustyle.fvwm
| [...]
`
Wha
