3 ms·
In practice, it is still easier to grep and edit config files in /etc (often commented), than to look for the needle in a haystack like gpedit, where, if locali
by vetinari 9y ago
In practice, it is still easier to grep and edit config files in /etc (often commented), than to look for the needle in a haystack like gpedit, where, if localized, you don't even know exact term you are looking for.
- kire456 9y agoNot really a fair comparison. For editing config files I often have to go to man pages to find out what the syntax is for the things I want (and sometimes, where to find the file). Especially if editing bash/zsh.rc, there is no hope of getting anything done without Google unless you already know how to do it. Conversely, most group policies I have ever needed were pointed out, including where to find them, after one web search, and their use is extensively documented in the config editor.
- vetinari 9y ago> here is no hope of getting anything done without Google > were pointed out, including where to find them, after one web search, Well, if you are doing that one web search, it doesn't matter whether the named key is for gui or text config. Except for that localization issue, if you find English string, it won't help you with localized one. Then there is the issue of the GP items themselves: many times you don't know whether to choose enable or disable, because double negatives FTW.
- proactivesvcs 9y agoIf you want a needle in a haystack, try finding out how to adjust network provider, binding and connection orders in the Windows GUI.