Merge pull request #4131 from stapelberg/bindingstate

binding state post-submit review fixes
This commit is contained in:
Orestis Floros
2020-06-17 11:22:23 +02:00
committed by GitHub
2 changed files with 3 additions and 2 deletions

View File

@@ -19,6 +19,7 @@ working. Please reach out to us in that case!
• configure: respect --program-suffix • configure: respect --program-suffix
• use exec to avoid leaving useless shell process • use exec to avoid leaving useless shell process
• ipc: always include the marks property (even if empty) • ipc: always include the marks property (even if empty)
• ipc: introduce GET_BINDING_STATE command
• introduce “tiling_from” and ”floating_from” criteria • introduce “tiling_from” and ”floating_from” criteria
• make dock client order deterministic (sorted by class/instance) as a • make dock client order deterministic (sorted by class/instance) as a
side effect, i3bars without an explicit bar-id will be sorted according side effect, i3bars without an explicit bar-id will be sorted according

View File

@@ -1,7 +1,7 @@
IPC interface (interprocess communication) IPC interface (interprocess communication)
========================================== ==========================================
Michael Stapelberg <michael@i3wm.org> Michael Stapelberg <michael@i3wm.org>
September 2017 June 2020
This document describes how to interface with i3 from a separate process. This This document describes how to interface with i3 from a separate process. This
is useful for example to remote-control i3 (to write test cases for example) or is useful for example to remote-control i3 (to write test cases for example) or
@@ -66,7 +66,7 @@ to do that).
| 9 | +GET_CONFIG+ | <<_config_reply,CONFIG>> | Returns the last loaded i3 config. | 9 | +GET_CONFIG+ | <<_config_reply,CONFIG>> | Returns the last loaded i3 config.
| 10 | +SEND_TICK+ | <<_tick_reply,TICK>> | Sends a tick event with the specified payload. | 10 | +SEND_TICK+ | <<_tick_reply,TICK>> | Sends a tick event with the specified payload.
| 11 | +SYNC+ | <<_sync_reply,SYNC>> | Sends an i3 sync event with the specified random value to the specified window. | 11 | +SYNC+ | <<_sync_reply,SYNC>> | Sends an i3 sync event with the specified random value to the specified window.
| 12 | +GET_BINDING_STATE+ | <<_binding_state_reply,BINDING_STATE>> | Request the current binding state, e.g. the currently active binding mode name. | 12 | +GET_BINDING_STATE+ | <<_binding_state_reply,BINDING_STATE>> | Request the current binding state, i.e. the currently active binding mode name.
|====================================================== |======================================================
So, a typical message could look like this: So, a typical message could look like this: