commands: fix documentation formatting mistakes for move command

master
Ian Fan 6 years ago
parent 7717c2231a
commit 453646b887

@ -22,7 +22,7 @@
static const char *expected_syntax =
"Expected 'move <left|right|up|down> <[px] px>' or "
"'move [--no-auto-back-and-forth] <container|window> [to] workspace <name>' or "
"'move [--no-auto-back-and-forth] <container|window|workspace> [to] output <name|direction>' or "
"'move <container|window|workspace> [to] output <name|direction>' or "
"'move <container|window> [to] mark <mark>'";
static struct sway_container *output_in_direction(const char *direction,

@ -132,7 +132,7 @@ They are expected to be used with *bindsym* or at runtime through *swaymsg*(1).
If unspecified, the default is 10 pixels. Pixels are ignored when moving
tiled containers.
*move* [absolute] position <pos_x> [px] <pos_y> [px]
*move* [absolute] position <pos\_x> [px] <pos\_y> [px]
Moves the focused container to the specified position.
*move* [absolute] position center|mouse
@ -154,7 +154,7 @@ They are expected to be used with *bindsym* or at runtime through *swaymsg*(1).
Moves the focused container to the previous or next workspace on this
output, wrapping around if already at the first or last workspace.
*move* container|window [to] workspace back_and_forth
*move* container|window [to] workspace back\_and\_forth
Moves the focused container to previously focused workspace.
*move* container|window|workspace [to] output <name>

Loading…
Cancel
Save