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?


  1. Posted March 9, 2008 at 9:17 am | Permalink

    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?

  2. Luke
    Posted March 9, 2008 at 11:53 pm | Permalink

    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.

  3. Posted March 10, 2008 at 12:04 am | Permalink

    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.)

  4. Posted March 10, 2008 at 11:17 pm | Permalink

    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.

  5. Posted March 11, 2008 at 1:40 am | Permalink

    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?