summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorElijah Newren <newren@gmail.com>2005-05-26 22:05:04 +0000
committerElijah Newren <newren@src.gnome.org>2005-05-26 22:05:04 +0000
commit1799ef6006da3349caa7f13361fe8e896f87b58d (patch)
tree74573197c24a34ebb367359a353d1dca0e4c916a /HACKING
parentbe499619443ddffd4fbb18c77629e0e5a12e1b41 (diff)
downloadmetacity-1799ef6006da3349caa7f13361fe8e896f87b58d.tar.gz
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
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING8
1 files changed, 5 insertions, 3 deletions
diff --git a/HACKING b/HACKING
index 640f0ecd..7557f8c1 100644
--- a/HACKING
+++ b/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.