aboutsummaryrefslogtreecommitdiffstats
path: root/swaymsg/swaymsg.1.scd
Commit message (Collapse)AuthorAge
* Add note on quoting to swaymsg manpageLibravatar Campbell Vertesi2020-07-15
| | | | (cherry picked from commit acbe9028157c67eb3937299ff86e5ee26816a408)
* i3-compat: add GET_BINDING_STATE IPC commandLibravatar Jason Nader2020-06-14
|
* swaymsg.1: fix typosLibravatar Martin Michlmayr2019-09-12
|
* swaymsg.1: fix description of --prettyLibravatar Martin Michlmayr2019-09-10
|
* swaymsg.1: add tip about two hyphens for commandsLibravatar Brian Ashworth2019-08-13
| | | | | | This adds a tip to the command section about using two hyphens before a command to signal that no swaymsg options will follow to allow for sway commands with leading hyphens.
* swaymsg: return 2 for sway errorsLibravatar Brian Ashworth2019-08-06
| | | | | | This mirrors a change in i3 4.17 that returns 2 for errors from sway, including invalid command, command failed, and invalid subscription requests
* Add -p/--pretty option to swaymsgLibravatar Peter Grayson2019-03-08
| | | | | | | | | | | This new option forces pretty (non-raw/non-JSON) output. By default, when not using a tty, swaymsg outputs using the "raw" format. This makes it impossible to, for example, pipe the pretty output to a pager such as `less` since piping does not use a tty. The new -p/--pretty option gives the user explicit control over the output format while retaining the default tty-dependent behavior. Signed-off-by: Peter Grayson <pete@jpgrayson.net>
* Add sway-ipc.7.scd to document IPC protocolLibravatar Brian Ashworth2019-02-27
| | | | | | | This add `sway-ipc.7.scd` that documents the IPC protocol. This also increased the minimum scdoc version from 1.8.1 to 1.9.0 to allow for table cells to be continued on the following line
* 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
generated by cgit v1.2.3-54-g00ecf (git 2.45.1) at 2024-05-27 20:52:02 +0000