docs/debugging: make it clearer that you need to reload i3

[i3/i3] / docs / debugging

diff --git a/docs/debugging b/docs/debugging
index 5187c529b4ed7ba69c088e11fcb8c33b4e3a8782..55197753c0d03ffffff82097f00ebab1c9d0069c 100644 (file)
--- a/docs/debugging
+++ b/docs/debugging
@@ -93,6 +93,11 @@ issue with the software in question, not i3.
 
 == Obtaining the debug logfile
 
+Please note that log files may contain sensitive data such as window titles.
+The best way to avoid submitting such information is to only run the necessary
+applications to reproduce the behavior when saving the log file. This will also
+make analyzing the log file easier.
+
 No matter whether i3 misbehaved in some way without crashing or whether it just
 crashed, the logfile provides all information necessary to debug the problem.
 
@@ -148,10 +153,11 @@ 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:
+To debug i3bar problems, add +verbose yes+ to all +bar {}+ blocks in your i3
+config, reload your config and then restart all i3bar instances like this:
 
 ---------------------------------------------------------------------
+$ i3 reload
 $ killall i3bar
 $ for c in $(i3-msg -t get_bar_config | python -c \
       'import json,sys;print("\n".join(json.load(sys.stdin)))'); do \