From: Michael Stapelberg <michael@stapelberg.de>
Date: Sat, 27 Mar 2010 14:30:09 +0000 (+0100)
Subject: mention -V -d all in docs/debugging
X-Git-Tag: 3.e~6^2~13
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=996884db180576e553836b613164f689dc1e0536;p=i3%2Fi3

mention -V -d all in docs/debugging
---

diff --git a/docs/debugging b/docs/debugging
index ca680f24..d52edea9 100644
--- 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