I 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

I 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/