Bruce Stephens <b.stephens_at_isode.com> writes:
> tma_at_nettest.dk writes:
>
> > I want to use TCL as the configuration language of fvwm instead of
> > the current command set. The reason for using TCL and not perl,
> > slang or any other configuration language, was to make the new
> > TCL-based configuration files completely backward compatible with
> > the current configuration files.
>
> Ah. Clever. Just looking at my .fvwm2rc suggests it's not entirely
> Tcl-friendly, but it's very close. Specifically, the function
> definitions have + as the first word, so you'd need to keep track of
> what the last definition was or something. And the module definition
> lines are weird: you'd presumably have to use something nasty like
> redefining unknown.
True!
Of cause, we would want to add a new more TCL friendly module
definition, which shouldn't be too hard... When everybody has
converted to the new configuration language (2-3 years), the
compability stuff can be removed...
/tonny
--
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 Apr 30 1998 - 07:48:58 BST