| |||||||||||||
Quotes of the weekQuotes of the weekPosted Feb 3, 2011 15:11 UTC (Thu) by drag (subscriber, #31333)In reply to: Quotes of the week by drag Parent article: Quotes of the week
Oh. And migrating through miles of GUI configuration dialogs is miserable.
Id take a gconf-editor or dconf-editor over a GUI configuration anytime, except for some certain common things.
I have never had a problem with editing configurations directly. Just as long as the option is there and it is documented somewhere.
To me the real fix is just documenting the options on some wiki somewhere. It shouldn't be difficult as 90% of the documentation can be auto-generated. That is really what is needed.
(Log in to post comments)
Quotes of the week Posted Feb 3, 2011 17:43 UTC (Thu) by jospoortvliet (subscriber, #33164) [Link]
He, shows how ppl are different. If something is only configurable from some obscure text file - forget about it, I won't even try. I'm not going to wade through loads of key-value pairs with weird names. Give me a well-designed (so not like compiz) configuration screen, preferably with a good search function build in :D
Quotes of the week Posted Feb 6, 2011 23:03 UTC (Sun) by gmaxwell (subscriber, #30048) [Link]
I run a distribution because I don't want to micromanage-with-maximum-difficulty every little detail of my system.
If you're going to continue to force me to use the freeking registry editor to get the behavior I want from my system, then I might as well be rolling my own.
Documenting something "on a wiki" someplace doesn't help me when I'm on an airplane and want to continue to listen to music with my screen closed. The only way I'm going to have a chance of having that kind of detailed knowledge when I need it is if I build the whole system "from scratch".
I agree that this is a reasonable default, even though it's not something that I'd want, but the lack of a readily accessible preference is just obnoxious.
|
|||||||||||||