I admit that I don't see any particular need to make the entire
configuration file built around (or parsed through) a language if one
just wants to improve some bits of it (say, the ability to have more
sophisticated functions). I semi-agree that the easiest way to get
more sophisticated functions may be to find a small (and hopefully
elegant) extension language to stick into fvwm2.
The fvwm2 configuration language is already very optimized for what it
does (which is the natural state of configuration languages). I can't
but think that any replacement that was trying to be a general purpose
language would be worse.
- cks
--
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 Fri May 01 1998 - 16:20:09 BST