docs/debugging: make it clearer that you need to reload i3
This commit is contained in:
parent
c95d6e328e
commit
3f259d0e83
|
@ -153,10 +153,11 @@ length limitations) or flood kicks.
|
||||||
|
|
||||||
== Debugging i3bar
|
== Debugging i3bar
|
||||||
|
|
||||||
To debug i3bar problems, add +verbose yes+ to all +bar {}+ blocks in your i3 config
|
To debug i3bar problems, add +verbose yes+ to all +bar {}+ blocks in your i3
|
||||||
and then restart all i3bar instances like this:
|
config, reload your config and then restart all i3bar instances like this:
|
||||||
|
|
||||||
---------------------------------------------------------------------
|
---------------------------------------------------------------------
|
||||||
|
$ i3 reload
|
||||||
$ killall i3bar
|
$ killall i3bar
|
||||||
$ for c in $(i3-msg -t get_bar_config | python -c \
|
$ for c in $(i3-msg -t get_bar_config | python -c \
|
||||||
'import json,sys;print("\n".join(json.load(sys.stdin)))'); do \
|
'import json,sys;print("\n".join(json.load(sys.stdin)))'); do \
|
||||||
|
|
Loading…
Reference in New Issue