I am for having a second file, that Config.hs imports, which provides each option as a Maybe. so say GuiGeneratedConfig.hs could provide Just 8 for border width, and Config.hs would define border width as borderwidth=(phsedocode as I've forgoten the function) if ggborderwidth is a just, then ggborderwidth, else 7
<br>that way the user could in their Config.hs, put whatever they wanted, and it could be replaced in GuiGeneratedConfig.hs, without modifying the old Config.hs.<br><br>I think that hotkeys would be best done by concatinating gghotkeys, with a filter so that if gghotkeys conflicted, it would overwrite the event for that hotkey.
<br>I DO NOT think that the program that makes GuiGeneratedConfig.hs belongs in contrib, I think it should be an entirely separate executable.<br>Timothy.<br><br><div><span class="gmail_quote">On 9/17/07, <b class="gmail_sendername">
Xiao-Yong Jin</b> <<a href="mailto:xj2106@columbia.edu">xj2106@columbia.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sam Walters <<a href="mailto:sam.walters@gmail.com">sam.walters@gmail.com</a>> writes:<br><br>> On Fri, Sep 14, 2007 at 07:35:22PM -0400, Xiao-Yong Jin wrote:<br>> :| It would be possible to make a GUI-based utility to
<br>> :| configure some simple behaviours through some variables.<br>> :| However, maintaining a Config.hs file is indispensable to<br>> :| make xmonad highly configurable.<br>><br>> I think there has been an unspoken assumption that having a configuration
<br>> utility excludes having a user-modifiable Config.hs file. If the<br><br>I would like a utility that can modify an existing Config.hs<br>file. Probably, some special mark-ups in the file could<br>permit this. Something like the customize-* functions in
<br>Emacs would do.<br><br>Of course, it could also be a separated file. We could have<br>two configuration files. One is automatically generated by<br>the utility, and the other can be customized by the user.<br>Some programs also do that.
<br><br>><br>> utility generates a fresh Config.hs instead of modifying<br>> an existing one, you get the best of both worlds. The<br>> user would have the choice of using the generated file,<br>> modifying the generated file or using a file that came
<br>> from another source.<br><br>In that case, you could only use that utility once, if you<br>want to modify it a bit. But I don't think that utility<br>is meant to be used only once.<br><br>><br>><br>> Sam
<br>><br>><br>> --<br>> Do not spoil what you have by desiring what you have not; remember that what<br>> you now have was once among the things you only hoped for.<br>> -- Epicurus
<br>> _______________________________________________<br>> Xmonad mailing list<br>> <a href="mailto:Xmonad@haskell.org">Xmonad@haskell.org</a><br>> <a href="http://www.haskell.org/mailman/listinfo/xmonad">http://www.haskell.org/mailman/listinfo/xmonad
</a><br>><br>><br><br>--<br> c/* __o/*<br> <\ * (__<br> */\ <<br>_______________________________________________<br>Xmonad mailing list<br><a href="mailto:Xmonad@haskell.org">Xmonad@haskell.org
</a><br><a href="http://www.haskell.org/mailman/listinfo/xmonad">http://www.haskell.org/mailman/listinfo/xmonad</a><br></blockquote></div><br><br clear="all"><br>-- <br>-<br>Tim<br><a href="mailto:tim.thelion@gmail.com">tim.thelion@gmail.com
</a>