mention -V -d all in docs/debugging

diff --git a/docs/debugging b/docs/debugging
index ca680f24ce20e8f4b4a83881e72728f91ea1648e..d52edea9d02301dcc10ac843abb3901d4f46865a 100644 (file)
--- a/docs/debugging
+++ b/docs/debugging
@@ -1,7 +1,7 @@
 Debugging i3: How To
 ====================
 Michael Stapelberg <michael+i3@stapelberg.de>
-April 2009
+March 2010
 
 This document describes how to debug i3 suitably for sending us useful bug
 reports, even if you have no clue of C programming.
@@ -12,14 +12,14 @@ debugging and/or need further help, do not hesitate to contact us!
 
 == Enabling logging
 
-i3 spits out much information onto stdout. To have a clearly defined place
-where log files will be saved, you should redirect stdout and stderr in
-xsession. While you’re at it, putting each run of i3 in a separate log file
-with date/time in it is a good idea to not get confused about the different
-log files later on.
+i3 spits out much information onto stdout, if told so. To have a clearly
+defined place where log files will be saved, you should redirect stdout and
+stderr in xsession. While you’re at it, putting each run of i3 in a separate
+log file with date/time in it is a good idea to not get confused about the
+different log files later on.
 
 --------------------------------------------------------------------
-exec /usr/bin/i3 >/home/michael/i3/i3log-$(date +'%F-%k-%M-%S') 2>&1
+exec /usr/bin/i3 -V -d all >/home/michael/i3/i3log-$(date +'%F-%k-%M-%S') 2>&1
 --------------------------------------------------------------------
 
 == Enabling core dumps