aboutsummaryrefslogtreecommitdiffstats
path: root/swaymsg/swaymsg.1.scd
Commit message (Collapse)AuthorAge
* Implement support for swaymsg -t SUBSCRIBE [-m]Libravatar Brian Ashworth2018-11-28
| | | | | | | | | | | | | | | | | | | | | 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']"`
* document swaymessage type for get_seatsLibravatar madblobfish2018-11-04
|
* ipc: add tick eventLibravatar Ian Fan2018-08-01
|
* Remove `clipboard` command and `get_clipboard` messageLibravatar emersion2018-07-10
|
* Add get_config message type to ipcLibravatar Ian Fan2018-07-10
|
* Add get_binding_modes message type to ipcLibravatar Ian Fan2018-07-10
|
* Add swaylock(1) and swaymsg(1)Libravatar Drew DeVault2018-05-11