Comments on: –debug? http://blogs.gnome.org/metacity/2008/03/09/debug/ "Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios." Sun, 26 Sep 2010 15:08:40 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Thomas Thurman http://blogs.gnome.org/metacity/2008/03/09/debug/comment-page-1/#comment-252 Thomas Thurman Tue, 11 Mar 2008 01:40:19 +0000 http://blogs.gnome.org/metacity/2008/03/09/debug/#comment-252 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? 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?

]]> By: Federico Mena http://blogs.gnome.org/metacity/2008/03/09/debug/comment-page-1/#comment-251 Federico Mena Mon, 10 Mar 2008 23:17:55 +0000 http://blogs.gnome.org/metacity/2008/03/09/debug/#comment-251 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. 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.

]]> By: Thomas Thurman http://blogs.gnome.org/metacity/2008/03/09/debug/comment-page-1/#comment-249 Thomas Thurman Mon, 10 Mar 2008 00:04:16 +0000 http://blogs.gnome.org/metacity/2008/03/09/debug/#comment-249 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.) 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.)

]]> By: Luke http://blogs.gnome.org/metacity/2008/03/09/debug/comment-page-1/#comment-248 Luke Sun, 09 Mar 2008 23:53:53 +0000 http://blogs.gnome.org/metacity/2008/03/09/debug/#comment-248 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. 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.

]]> By: Mikkel Kamstrup Erlandsen http://blogs.gnome.org/metacity/2008/03/09/debug/comment-page-1/#comment-240 Mikkel Kamstrup Erlandsen Sun, 09 Mar 2008 09:17:24 +0000 http://blogs.gnome.org/metacity/2008/03/09/debug/#comment-240 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? 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?

]]>