diff options
-rw-r--r-- | sway/sway.5.scd | 19 |
1 files changed, 16 insertions, 3 deletions
diff --git a/sway/sway.5.scd b/sway/sway.5.scd index e04c5fbf..5f38cb51 100644 --- a/sway/sway.5.scd +++ b/sway/sway.5.scd | |||
@@ -282,7 +282,7 @@ runtime. | |||
282 | 282 | ||
283 | for_window <criteria> move container to output <output> | 283 | for_window <criteria> move container to output <output> |
284 | 284 | ||
285 | *bindsym* [--release|--locked] [--input-device=<device>] [--no-warn] <key combo> <command> | 285 | *bindsym* [--whole-window] [--border] [--exclude-titlebar] [--release] [--locked] [--input-device=<device>] [--no-warn] <key combo> <command> |
286 | Binds _key combo_ to execute the sway command _command_ when pressed. You | 286 | Binds _key combo_ to execute the sway command _command_ when pressed. You |
287 | may use XKB key names here (*xev*(1) is a good tool for discovering these). | 287 | may use XKB key names here (*xev*(1) is a good tool for discovering these). |
288 | With the flag _--release_, the command is executed when the key combo is | 288 | With the flag _--release_, the command is executed when the key combo is |
@@ -294,11 +294,24 @@ runtime. | |||
294 | the _--no-warn_ flag. | 294 | the _--no-warn_ flag. |
295 | 295 | ||
296 | Mouse buttons can either be specified in the form _button[1-9]_ or by using | 296 | Mouse buttons can either be specified in the form _button[1-9]_ or by using |
297 | the name of the event code (ex _BTN_LEFT_ or _BTN_RIGHT_). For the former | 297 | the name of the event code (ex _BTN\_LEFT_ or _BTN\_RIGHT_). For the former |
298 | option, the buttons will be mapped to their values in X11 (1=left, 2=middle, | 298 | option, the buttons will be mapped to their values in X11 (1=left, 2=middle, |
299 | 3=right, 4=scroll up, 5=scroll down, 6=scroll left, 7=scroll right, 8=back, | 299 | 3=right, 4=scroll up, 5=scroll down, 6=scroll left, 7=scroll right, 8=back, |
300 | 9=forward). For the latter option, you can find the event names using | 300 | 9=forward). For the latter option, you can find the event names using |
301 | _libinput debug-events_. | 301 | _libinput debug-events_. |
302 | |||
303 | _--whole-window_, _--border_, and _--exclude-titlebar_ are mouse-only options | ||
304 | which affect the region in which the mouse bindings can be triggered. By | ||
305 | default, mouse bindings are only triggered when over the title bar. With the | ||
306 | _--border_ option, the border of the window will be included in this region. | ||
307 | With the _--whole-window_ option, the cursor can be anywhere over a window | ||
308 | including the title, border, and content. _--exclude-titlebar_ can be used in | ||
309 | conjunction with any other option to specify that the titlebar should be | ||
310 | excluded from the region of consideration. | ||
311 | |||
312 | There is currently, however, no way to execute a mouse binding over a layer | ||
313 | surface (which includes the background of an empty workspace). This behaviour | ||
314 | is carried over from i3. | ||
302 | 315 | ||
303 | Example: | 316 | Example: |
304 | ``` | 317 | ``` |
@@ -306,7 +319,7 @@ runtime. | |||
306 | bindsym Mod1+Shift+f exec firefox | 319 | bindsym Mod1+Shift+f exec firefox |
307 | ``` | 320 | ``` |
308 | 321 | ||
309 | *bindcode* [--release|--locked] [--input-device=<device>] [--no-warn] <code> <command> | 322 | *bindcode* [--whole-window] [--border] [--exclude-titlebar] [--release] [--locked] [--input-device=<device>] [--no-warn] <code> <command> |
310 | is also available for binding with key/button codes instead of key/button names. | 323 | is also available for binding with key/button codes instead of key/button names. |
311 | 324 | ||
312 | *client.<class>* <border> <background> <text> <indicator> <child_border> | 325 | *client.<class>* <border> <background> <text> <indicator> <child_border> |