4 ms·
I understand that it isn't a nice idea having code and configuration mixed together and that splitting them would be preferable. However, howm takes less than 1
by hunt 12y ago
I understand that it isn't a nice idea having code and configuration mixed together and that splitting them would be preferable. However, howm takes less than 1 second to compile on my laptop, once you have a configuration that you like you'll rarely change it and I feel that having the configuration in code makes it easier for hackers to find subtle new ways of customising howm.
A downside that I can see to using a header file for configuration is that a compile is required for installation and configuration. I don't see this as being too much of an issue as I don't plan on making howm available as a binary, so a compiler would be required anyway.
- rakoo 12y agoI think we can all agree that once a good setup is found, you don't change it that much; recompiling is ok as long as it's fast. The point of GP is that since config.h is part of the standard distribution, any local modification should be overwritten (or discarded) upon updating the software, or the user has to maintain a local "fork" with his custom config.h. You should get inspiration from what suckless does [0]. It uses the same idea of config through header, and the "solution" is workable for all involved parties. [0] http://dwm.suckless.org/customisation/ http://dwm.suckless.org/customisation/