From f8a52f0862744160405404d9cac03289e01d73f0 Mon Sep 17 00:00:00 2001
From: =?utf8?q?Ingo=20B=C3=BCrk?= <ingo.buerk@tngtech.com>
Date: Sun, 19 Apr 2015 22:37:37 +0200
Subject: [PATCH] Provide instructions on how to debug i3bar

---
 docs/debugging | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/docs/debugging b/docs/debugging
index 1253b0c5..400a6b2b 100644
--- a/docs/debugging
+++ b/docs/debugging
@@ -121,3 +121,19 @@ When debugging with us in IRC, be prepared to use a so called nopaste service
 such as http://nopaste.info or http://pastebin.com because pasting large
 amounts of text in IRC sometimes leads to incomplete lines (servers have line
 length limitations) or flood kicks.
+
+== Debugging i3bar
+
+To debug i3bar problems, add +verbose yes+ to all +bar {}+ blocks in your i3 config
+and then restart all i3bar instances like this:
+
+---------------------------------------------------------------------
+$ killall i3bar
+$ for c in $(i3-msg -t get_bar_config | python -c \
+      'import json,sys;print("\n".join(json.load(sys.stdin)))'); do \
+    (i3bar --bar_id=$c >i3bar.$c.log 2>&1) & \
+  done;
+---------------------------------------------------------------------
+
+There will now be +i3bar.*.log+ files in your current directory that you can provide
+in your bug report.
-- 
2.39.5