From a8a239e2f1ca6236c2b8f7cebf0cc37890e77ec0 Mon Sep 17 00:00:00 2001 From: Brian Ashworth Date: Sun, 4 Aug 2019 02:02:13 -0400 Subject: [PATCH] swaymsg: return 2 for sway errors This mirrors a change in i3 4.17 that returns 2 for errors from sway, including invalid command, command failed, and invalid subscription requests --- swaymsg/main.c | 2 +- swaymsg/swaymsg.1.scd | 13 +++++++++++++ 2 files changed, 14 insertions(+), 1 deletion(-) diff --git a/swaymsg/main.c b/swaymsg/main.c index f288d4a0..a018a68e 100644 --- a/swaymsg/main.c +++ b/swaymsg/main.c @@ -475,7 +475,7 @@ int main(int argc, char **argv) { ret = 1; } else { if (!success(obj, true)) { - ret = 1; + ret = 2; } if (!quiet && (type != IPC_SUBSCRIBE || ret != 0)) { if (raw) { diff --git a/swaymsg/swaymsg.1.scd b/swaymsg/swaymsg.1.scd index 1bcf956a..bcddf35b 100644 --- a/swaymsg/swaymsg.1.scd +++ b/swaymsg/swaymsg.1.scd @@ -86,6 +86,19 @@ _swaymsg_ [options...] [message] provided in the form of a valid JSON array. If any of the types are invalid or if an valid JSON array is not provided, this will result in an failure. +# RETURN CODES + +*0* + Success + +*1* + swaymsg errors such as invalid syntax, unable to connect to the ipc socket + or unable to parse sway's reply + +*2* + Sway returned an error when processing the command (ex. invalid command, + command failed, and invalid subscription request) + # SEE ALSO *sway*(5) *sway-bar*(5) *sway-input*(5) *sway-output*(5) *sway-ipc*(7)