aboutsummaryrefslogtreecommitdiffstats
path: root/swaybar
diff options
context:
space:
mode:
authorLibravatar Hubert Hirtz <hubert@hirtzfr.eu>2020-08-03 16:08:05 +0200
committerLibravatar Simon Ser <contact@emersion.fr>2020-08-04 10:39:29 +0200
commitc5c632aaae78b1e6ac8c28341e782541bd138599 (patch)
treec67fddac973b8ed646ced20c98fa62de849ef293 /swaybar
parentdocument force_display_urgency_hint (diff)
downloadsway-c5c632aaae78b1e6ac8c28341e782541bd138599.tar.gz
sway-c5c632aaae78b1e6ac8c28341e782541bd138599.tar.zst
sway-c5c632aaae78b1e6ac8c28341e782541bd138599.zip
Document required '\n' in swaybar-protocol
The following statusbar output is not considered by sway to be following the swaybar-protocol: {"version":1}[[{"full_text":"2.89","urgent":false}], However this one is: {"version":1}\n[[{"full_text":"2.89","urgent":false}], Both outputs contain a header with the required values and an unfinished array of objects with the required values, but the first one is showed verbatim.
Diffstat (limited to 'swaybar')
-rw-r--r--swaybar/swaybar-protocol.7.scd8
1 files changed, 4 insertions, 4 deletions
diff --git a/swaybar/swaybar-protocol.7.scd b/swaybar/swaybar-protocol.7.scd
index 3f6a712c..2ecd2a7e 100644
--- a/swaybar/swaybar-protocol.7.scd
+++ b/swaybar/swaybar-protocol.7.scd
@@ -8,10 +8,10 @@ swaybar-protocol - JSON status line protocol for swaybar
8 8
9swaybar defines the following JSON protocol to specify what information is 9swaybar defines the following JSON protocol to specify what information is
10displayed in the status line on the right side of swaybar. The protocol 10displayed in the status line on the right side of swaybar. The protocol
11comprises a header, that is a JSON object, followed by an infinite JSON 11comprises a header, that is a JSON object, followed by a newline (*0x0A*),
12array that represents the information to display. All communication is done by 12followed by an infinite JSON array that represents the information to display.
13writing the status line to standard output and reading events from standard 13All communication is done by writing the status line to standard output and
14input. 14reading events from standard input.
15 15
16# HEADER 16# HEADER
17 17