Add a clarification that METACITY_VERBOSE needs to be accompanied by
2005-05-26 Elijah Newren <newren@gmail.com> * HACKING: Add a clarification that METACITY_VERBOSE needs to be accompanied by METACITY_USE_LOGFILE
This commit is contained in:
parent
be49961944
commit
1799ef6006
2 changed files with 10 additions and 3 deletions
|
@ -1,3 +1,8 @@
|
|||
2005-05-26 Elijah Newren <newren@gmail.com>
|
||||
|
||||
* HACKING: Add a clarification that METACITY_VERBOSE needs to be
|
||||
accompanied by METACITY_USE_LOGFILE
|
||||
|
||||
2005-05-26 Elijah Newren <newren@gmail.com>
|
||||
|
||||
* src/window.c (meta_window_configure_request): Patch from Greg
|
||||
|
|
8
HACKING
8
HACKING
|
@ -101,9 +101,11 @@ Debugging information
|
|||
useful to get more information than just warnings. You can set
|
||||
METACITY_VERBOSE to do that, like so:
|
||||
METACITY_VERBOSE=1 METACITY_USE_LOGFILE=1 metacity --replace
|
||||
There are also other flags, such as METACITY_DEBUG, most of which I
|
||||
haven't tried and don't know what they do. Go to the source code
|
||||
directory and run
|
||||
(note that METACITY_VERBOSE=1 cannot be used without
|
||||
METACITY_USE_LOGFILE=1 or metacity will crash). There are also
|
||||
other flags, such as METACITY_DEBUG, most of which I haven't tried
|
||||
and don't know what they do. Go to the source code directory and
|
||||
run
|
||||
grep "METACITY_" * | grep getenv
|
||||
to find out what the other ones are.
|
||||
|
||||
|
|
Loading…
Reference in a new issue