Issue 230: Modular config support http://code.google.com/p/xmonad/issues/detail?id=230 Comment #1 by gwern0: There's always option 'd', do nothing. Option a requires a major user intervention; if we were going to do that, then I think we should blow our capital on something more valuable. Option b harms usability. Option c may not harm usability, but if it does, it'll really hurt that user who runs into a problem. Option d is well-understood; there doesn't seem to be a huge need for multi-modular xmonad.hses; and I'm not convinced that one *should* have xmonad.hses which are that enormous. If they are that large, then perhaps one should be looking into contributing modules or functions or features upstream, seeing whether there are better ways to accomplish things, or just generally rethinking the xmonad.hs. -- 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