From d27a5e1cb0f14e939d47497ebc49cfb422cc947b Mon Sep 17 00:00:00 2001 From: Konstantin Pospelov Date: Mon, 18 Feb 2019 21:39:37 +0300 Subject: [PATCH] bindsym: update the man page to include --to-code --- sway/sway.5.scd | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/sway/sway.5.scd b/sway/sway.5.scd index 230ceeec2..9fe51c335 100644 --- a/sway/sway.5.scd +++ b/sway/sway.5.scd @@ -327,7 +327,7 @@ runtime. for_window move container to output -*bindsym* [--whole-window] [--border] [--exclude-titlebar] [--release] [--locked] [--input-device=] [--no-warn] +*bindsym* [--whole-window] [--border] [--exclude-titlebar] [--release] [--locked] [--to-code] [--input-device=] [--no-warn] Binds _key combo_ to execute the sway command _command_ when pressed. You may use XKB key names here (*xev*(1) is a good tool for discovering these). With the flag _--release_, the command is executed when the key combo is @@ -338,6 +338,10 @@ runtime. overwrite a binding, swaynag will give you a warning. To silence this, use the _--no-warn_ flag. + Bindings to keysyms are layout-dependent. This can be changed with the + _--to-code_ flag. In this case, the keysyms will be translated into the + corresponding keycodes in the first configured layout. + Mouse bindings operate on the container under the cursor instead of the container that has focus. Mouse buttons can either be specified in the form _button[1-9]_ or by using the name of the event code (ex _BTN\_LEFT_ or