What do people think about adding a new “metacity –debug” switch which did the same as the logging environment variables? Would users find it easier to use or remember when necessary?
–debug?
Published by
What do people think about adding a new “metacity –debug” switch which did the same as the logging environment variables? Would users find it easier to use or remember when necessary?
That would be sweet, and option to send the debugging info to stdout would be even more handy I think – or perhaps this is already possible?
What about a GConf key? It could be a lot easier to give instructions to non-expert users about turning on and off debug that a commandline variable or switch, given that Metacity is normally just launched at the session start.
Oo, yes. I like that idea. I wonder whether there would be something in gnome-control-center which controlled it or whether we’d have to tell them how to go to gconf-editor and turn it on. (I suppose we could have a hot key, as well, but there are disadvantages to stealing a key combination from all apps for ever and always, just for this.)
Feel free to peruse http://www.gnome.org/~federico/news-2007-04.html#sabayon-logging
Ignore the part on Sabayon’s internals. The meat of that post is the thoughts at the end, about how to make a logging system that is friendly to users. This applies especially to things like Metacity, which you can’t easily launch from a shell.
Luke’s idea of using a GConf key is great, and it actually matches the behavior I wanted for Sabayon.
Does Sabayon log all the time it’s running, then, and you only upload the current one when there’s a problem? How do you stop the set of logs from growing indefinitely?