Sam Walters
On Fri, Sep 14, 2007 at 07:35:22PM -0400, Xiao-Yong Jin wrote: :| It would be possible to make a GUI-based utility to :| configure some simple behaviours through some variables. :| However, maintaining a Config.hs file is indispensable to :| make xmonad highly configurable.
I think there has been an unspoken assumption that having a configuration utility excludes having a user-modifiable Config.hs file. If the
I would like a utility that can modify an existing Config.hs file. Probably, some special mark-ups in the file could permit this. Something like the customize-* functions in Emacs would do. Of course, it could also be a separated file. We could have two configuration files. One is automatically generated by the utility, and the other can be customized by the user. Some programs also do that.
utility generates a fresh Config.hs instead of modifying an existing one, you get the best of both worlds. The user would have the choice of using the generated file, modifying the generated file or using a file that came from another source.
In that case, you could only use that utility once, if you want to modify it a bit. But I don't think that utility is meant to be used only once.
Sam
-- Do not spoil what you have by desiring what you have not; remember that what you now have was once among the things you only hoped for. -- Epicurus _______________________________________________ Xmonad mailing list Xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad
-- c/* __o/* <\ * (__ */\ <