commit 9bac7e6558b8a8cffcc566a7006f6c9789085db6
parent acd3db4fe1f8bfabc2e9edb8ac6cff706fdfaaf3
Author: Brian Ashworth <bosrsf04@gmail.com>
Date: Mon, 12 Aug 2019 22:23:29 -0400
swaymsg.1: add tip about two hyphens for commands
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.
Diffstat:
1 file changed, 5 insertions(+), 0 deletions(-)
diff --git a/swaymsg/swaymsg.1.scd b/swaymsg/swaymsg.1.scd
@@ -46,6 +46,11 @@ _swaymsg_ [options...] [message]
See **sway**(5) for a list of commands.
+ Tip: If you are proving a command that contains a leading hyphen (_-_),
+ insert two hyphens (_--_) before the command to signal to swaymsg not to
+ parse anything beyond that point as an option. For example, use
+ _swaymsg -- mark --add test_ instead of _swaymsg mark --add test_
+
*get\_workspaces*
Gets a JSON-encoded list of workspaces and their status.