summaryrefslogtreecommitdiff
path: root/man/i3status.man
diff options
context:
space:
mode:
authorMichael Stapelberg <michael@stapelberg.de>2012-12-05 17:47:29 +0100
committerMichael Stapelberg <michael@stapelberg.de>2012-12-05 17:49:54 +0100
commit0a608d4af67fe59390f2e8931f61b664f48660db (patch)
tree89a7577bdf57512f1ab2313af9f7eb8d483b5c37 /man/i3status.man
parent0eeded8bc013857a5e8a2efbc20002a22502897e (diff)
make SIGUSR1 do nothing, so that killall -USR1 i3status will force an update
Sending SIGUSR1 will interrupt the nanosleep() and thus force a new iteration of i3status’s output loop. The signal handler itself is empty. Based on the question by ttjjss at http://faq.i3wm.org/question/854/how-to-force-status-bar-update/
Diffstat (limited to 'man/i3status.man')
-rw-r--r--man/i3status.man6
1 files changed, 6 insertions, 0 deletions
diff --git a/man/i3status.man b/man/i3status.man
index c14d8d2..3f7a924 100644
--- a/man/i3status.man
+++ b/man/i3status.man
@@ -378,6 +378,12 @@ Note that if you want to use the JSON output format (with colors in i3bar), you
need to use a slightly more complex wrapper script. There are examples in the
contrib/ folder, see http://code.i3wm.org/i3status/tree/contrib
+== SIGNALS
+
+When receiving +SIGUSR1+, i3status’s nanosleep() will be interrupted and thus
+you will force an update. You can use killall -USR1 i3status to force an update
+after changing the system volume, for example.
+
== SEE ALSO
+strftime(3)+, +date(1)+, +glob(3)+, +dzen2(1)+, +xmobar(1)+