summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorElijah Newren <newren@gmail.com>2005-10-21 00:22:38 +0000
committerElijah Newren <newren@src.gnome.org>2005-10-21 00:22:38 +0000
commit7c70749ae83050cac8001e6e8f62db9a7b2941b9 (patch)
treeda47832f28d7a6f1d45ddeba66fee942bcc6f834 /HACKING
parent37ced4cc3243e6e762d03357abbfb288ce8dd197 (diff)
downloadmetacity-7c70749ae83050cac8001e6e8f62db9a7b2941b9.tar.gz
metacity-7c70749ae83050cac8001e6e8f62db9a7b2941b9.tar.bz2
Clarify why METACITY_VERBOSE=1 is bad without META_USE_LOGFILE=1; point to
2005-10-20 Elijah Newren <newren@gmail.com> * HACKING: Clarify why METACITY_VERBOSE=1 is bad without META_USE_LOGFILE=1; point to bug 305091 for details.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING11
1 files changed, 6 insertions, 5 deletions
diff --git a/HACKING b/HACKING
index 1cc99bd..f1bd67d 100644
--- a/HACKING
+++ b/HACKING
@@ -107,11 +107,12 @@ 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
- (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
+ (note that METACITY_VERBOSE=1 can be problematic without
+ METACITY_USE_LOGFILE=1; avoid it unless running in from something that
+ won't be managed by the new Metacity--see bug 305091 for more details).
+ 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.