{ "success": true }+
X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=docs%2Fipc.html;h=350483e33f37c8463906ac6da522aa4867504de3;hb=a303c3a5ed951eb3795cb4c08f2972a8bdf93605;hp=34a55eaf82ac70a6b11b9509f6e6be4b59b23250;hpb=4f2a4ac4dccfadd56bbc349e10289bf8750a0e67;p=i3%2Fi3.github.io diff --git a/docs/ipc.html b/docs/ipc.html index 34a55ea..350483e 100644 --- a/docs/ipc.html +++ b/docs/ipc.html @@ -171,6 +171,12 @@ cellspacing="0" cellpadding="4">
Returns the last loaded i3 config.
10
SEND_TICK
Sends a tick event with the specified payload.
+ Reply to the SEND_TICK message. +
+{ "config": "font pango:monospace 8\nbindsym Mod4+q exit\n" }
The reply is a map containing the "success" member. After the reply was +received, the tick event has been written to all IPC connections which subscribe +to tick events. UNIX sockets are usually buffered, but you can be certain that +once you receive the tick event you just triggered, you must have received all +events generated prior to the SEND_TICK message (happened-before relation).
Example:
{ "success": true }+
+ Sent when the ipc client subscribes to the tick event (with "first": + true) or when any ipc client sends a SEND_TICK message (with "first": + false). +
+Example:
This event is triggered by a subscription to tick events or by a SEND_TICK +message.
Example (upon subscription):
{ + "first": true, + "payload": "" +}+
Example (upon SEND_TICK with a payload of arbitrary string):
{ + "first": false, + "payload": "arbitrary string" +}+
https://github.com/whitelynx/i3ipc (not maintained)
Find an example implementation of this technique in +https://github.com/i3/go-i3/blob/master/byteorder.go