3 ms·
An additional point is that most of the time config-dumps from a running program include ALL configuration settings. 95% of the time it's simply not important -
by XorNot 11y ago
An additional point is that most of the time config-dumps from a running program include ALL configuration settings. 95% of the time it's simply not important - what I actually want to know is "what is not set to its default".
Which means I need the config files.
I'm not against ALL comments - i.e. if something has a non-obvious external issue, that's worth noting. But people argue that the very verbose default comments, for example, should be left in - that's pointless, and potentially hazardous.
- semi-extrinsic 11y agoWhile I agree useless comments are bad, especially in production, is there any reason why you don't just have a macro in your editor (assuming vim here) to do :view :g/^\s*#/d (this sets vim into read-only mode and then deletes all comment lines, assuming # for comments).