Quoting Martin Kraemer:
[...]
mk> Or, using the Pipe mechanism I saw on this list earlier on (and which I
mk> think would be _very_ useful to include as a standard feature), one
mk> could easily write
mk> Read "| [ -f $HOME/.fvwm2rc ] && cat $HOME/.fvwm2rc || cat /usr/lib/X11/fvwm2/system.fvwm2rc"
This syntax is very misleading! A leading vertical bar ('|')
suggests, that the process will open the pipe for writing instead
of reading. It would be much better, if the 'Read' command will
check, if the last character in the filename argument is a
vertical bar and then use 'popen' instead of 'fopen'. Martins
example from above will than be written as
Read "[ -f $HOME/.fvwm2rc ] && ... ... m2/system.fvwm2rc |"
---------------------------------------------------------------^ !!
BTW: IMHO lines longer than 80 characters look very awful. One feature
I am missing at least in fvwm 1.24r is the possibility to introduce
continuation lines. Since the comment syntax of .fvwm[2]rc is shell
lookalike, it would make much sense to me, if a backslash ('\') as last
character in a line would cause the following newline to be ignored.
Regards, Peter
-=-=-
Peter Funk, Oldenburger Str.86, D-27777 Ganderkesee, Germany
office: +49 421 2041925 (ArtCom GmbH, Grazer Str.8, D-28359 Bremen)
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu May 30 1996 - 01:36:42 BST