Issue 230: Modular config support http://code.google.com/p/xmonad/issues/detail?id=230 Comment #3 by amdragon: All good points, though the premise, at least in my mind, was not for enormous xmonad.hses, but rather because Modularity is Good. I have lots of little things in my xmonad.hs like custom loggers and prompts, as I imagine many people do, for which it would make sense to isolate the code and dependencies in separate modules. Furthermore, encouraging people to modularize such code now would make it easy to move them into xmonad-contrib as they grew and become more generally useful. However, if this is an unusual way to use xmonad.hs, then I agree that providing two configuration options for the sake of modularity may be overkill (though I disagree that asking the user to rename a file at their convenience constitutes "major user intervention"). If there is a more warranted configuration change that requires user intervention anyways (such as the past one from Config.hs to xmonad.hs), then please take this issue into consideration. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings