aboutsummaryrefslogtreecommitdiff
path: root/swaymsg/swaymsg.1.scd
AgeCommit message (Collapse)Author
2021-10-15cross-reference further documentationJonas Große Sundrup
2021-10-15change incorrectly documented output typesJonas Große Sundrup
2021-10-15clarify the type of raw outputJonas Große Sundrup
2020-09-04swaymsg.1: expand tip for multi-word strings.Érico Rolim
Strings with commas inside, such as the ones used for xkb_{config,layout} commands, count as multi-word strings.
2020-08-05swaymsg.1: correct typoMark Stosberg
2020-07-15Add note on quoting to swaymsg manpageCampbell Vertesi
2020-06-14i3-compat: add GET_BINDING_STATE IPC commandJason Nader
2019-09-12swaymsg.1: fix typosMartin Michlmayr
2019-09-10swaymsg.1: fix description of --prettyMartin Michlmayr
2019-08-13swaymsg.1: add tip about two hyphens for commandsBrian Ashworth
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.
2019-08-06swaymsg: return 2 for sway errorsBrian Ashworth
This mirrors a change in i3 4.17 that returns 2 for errors from sway, including invalid command, command failed, and invalid subscription requests
2019-03-08Add -p/--pretty option to swaymsgPeter Grayson
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>
2019-02-27Add sway-ipc.7.scd to document IPC protocolBrian Ashworth
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
2018-11-28Implement support for swaymsg -t SUBSCRIBE [-m]Brian Ashworth
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']"`
2018-11-04document swaymessage type for get_seatsmadblobfish
2018-08-01ipc: add tick eventIan Fan
2018-07-10Remove `clipboard` command and `get_clipboard` messageemersion
2018-07-10Add get_config message type to ipcIan Fan
2018-07-10Add get_binding_modes message type to ipcIan Fan
2018-05-11Add swaylock(1) and swaymsg(1)Drew DeVault