From 1799ef6006da3349caa7f13361fe8e896f87b58d Mon Sep 17 00:00:00 2001 From: Elijah Newren Date: Thu, 26 May 2005 22:05:04 +0000 Subject: [PATCH] Add a clarification that METACITY_VERBOSE needs to be accompanied by 2005-05-26 Elijah Newren * HACKING: Add a clarification that METACITY_VERBOSE needs to be accompanied by METACITY_USE_LOGFILE --- ChangeLog | 5 +++++ HACKING | 8 +++++--- 2 files changed, 10 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 476fe6188..cb67fc8c2 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2005-05-26 Elijah Newren + + * HACKING: Add a clarification that METACITY_VERBOSE needs to be + accompanied by METACITY_USE_LOGFILE + 2005-05-26 Elijah Newren * src/window.c (meta_window_configure_request): Patch from Greg diff --git a/HACKING b/HACKING index 640f0ecd0..7557f8c19 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.