aboutsummaryrefslogtreecommitdiffstats
path: root/README.el.md
diff options
context:
space:
mode:
authorLibravatar Brian Ashworth <bosrsf04@gmail.com>2018-11-28 11:19:18 -0500
committerLibravatar Brian Ashworth <bosrsf04@gmail.com>2018-11-28 11:19:18 -0500
commitbf9a52bab0f8ae9b4ace43c7d9c75ece0c76b562 (patch)
tree812af4f8fee1f289bc244136ac21acca44de15b0 /README.el.md
parentMerge pull request #3211 from emersion/child-view-unmapped-segfault (diff)
downloadsway-bf9a52bab0f8ae9b4ace43c7d9c75ece0c76b562.tar.gz
sway-bf9a52bab0f8ae9b4ace43c7d9c75ece0c76b562.tar.zst
sway-bf9a52bab0f8ae9b4ace43c7d9c75ece0c76b562.zip
Implement support for swaymsg -t SUBSCRIBE [-m]
In `i3 4.16`, `i3-msg` can be used with the message type `subscribe` and has the ability to monitor for responses until killed. This adds support for both to swaymsg. If the JSON array of event types is malformed or contains an invalid event, sway will send a response with `success` set to `false`. If swaymsg sees this, it will not display the failure and exit. If the `subscribe` event is successful, swaymsg will wait for the first response and display that instead of the success message. If `-m/--monitor` is given, swaymsg will continue monitor for responses until killed or a malformed response is received. For the `subscribe` event, the responses will always be printed as JSON. If `-r/--raw` is given, the JSON will not be pretty printed, which may be preferred when monitoring due to there being multiple responses. Example: `swaymsg -t SUBSCRIBE -m "['window']"`
Diffstat (limited to 'README.el.md')
0 files changed, 0 insertions, 0 deletions