i3 FAQ - Individual question feed

i3 FAQ - Individual question feedhttps://faq.i3wm.org/questions/Frequently asked questions and answers about the i3 window managerenCopyright i3, 2012Mon, 27 Jul 2015 14:53:22 +0000Bind alt+tab to workspace nexthttps://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/Hi community, I have two small very related questions. A small legend (from xmodmap) for them: keycode 23 = Left Tab keycode 50 = Left Alt 1) Can I bind just alt+tab (without $mod) to `workspace next`? I currently have `bindcode $mod+23 workspace next`, which is fine, but I felt alt+tab is more natural. Can I do this without $mod? I tried `bindcode 23+50 workspace next`, but alt by itself switches workspaces if I do that. 2) The following bind does not work, I am not sure why: `bindcode $mod+50+23 workspace prev`. Well, it works: it binds $mod + shift, but not $mod +shift+tab. Thank you!Sun, 26 Jul 2015 19:10:44 +0000https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/Answer by Adaephon for Hi community, I have two small very related questions. A small legend (from xmodmap) for them: <pre><code>keycode 23 = Left Tab keycode 50 = Left Alt </code></pre> 1) Can I bind just alt+tab (without $mod) to <code>workspace next</code>? I currently have <code>bindcode $mod+23 workspace next</code>, which is fine, but I felt alt+tab is more natural. Can I do this without $mod? I tried <code>bindcode 23+50 workspace next</code>, but alt by itself switches workspaces if I do that. 2) The following bind does not work, I am not sure why: <code>bindcode $mod+50+23 workspace prev</code>. Well, it works: it binds $mod + shift, but not $mod +shift+tab. Thank you! https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?answer=6351#post-id-6351You can get the expected behaviour with `bindcode`: bindcode Mod1+23 workspace next bindcode Mod1+Shift+23 workspace prev `bindcode` expects a key code only for the last key, not the modifiers. As you noticed *i3* stops parsing the keychain for `bindcode` when encountering the first key code. As per the [User's Guide](http://i3wm.org/docs/userguide.html#keybindings) the syntax for the `bindcode` setting is bindcode [--release] [Modifiers+]keycode command Where `[Modifiers+]` is a optional (`+`-separated) list of any of these: `Mod1`, `Mod2`, `Mod3`, `Mod4`, `Mod5`, `Shift`, `Control` and `Mode_switch`. Not all of which may be defined for your keyboard layout (check with `xmodmap -pm`). `Mod1` commonly maps to **Alt** an `Mod4` to **Super** (aka **Win-Key**). `$mod` is just a variable (probably set to `Mod4` in your case) which *i3* just replaces when parsing the configuration. It is not an integral part of all possible key bindings. In *i3* you can bind any key (even modifiers themselves) without any modifiers or with any combination of modifiers. ---- Similarly `bindsym` expects the same list of modifiers and not the key symbols of the modifiers.Mon, 27 Jul 2015 07:48:04 +0000https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?answer=6351#post-id-6351Comment by Airblader for You can get the expected behaviour with <code>bindcode</code>: <pre><code>bindcode Mod1+23 workspace next bindcode Mod1+Shift+23 workspace prev </code></pre> <code>bindcode</code> expects a key code only for the last key, not the modifiers. As you noticed i3 stops parsing the keychain for <code>bindcode</code> when encountering the first key code. As per the <a href="http://i3wm.org/docs/userguide.html#keybindings">User's Guide</a> the syntax for the <code>bindcode</code> setting is <pre><code>bindcode [--release] [Modifiers+]keycode command </code></pre> Where <code>[Modifiers+]</code> is a optional (<code>+</code>-separated) list of any of these: <code>Mod1</code>, <code>Mod2</code>, <code>Mod3</code>, <code>Mod4</code>, <code>Mod5</code>, <code>Shift</code>, <code>Control</code> and <code>Mode_switch</code>. Not all of which may be defined for your keyboard layout (check with <code>xmodmap -pm</code>). <code>Mod1</code> commonly maps to Alt an <code>Mod4</code> to Super (aka Win-Key). <code>$mod</code> is just a variable (probably set to <code>Mod4</code> in your case) which i3 just replaces when parsing the configuration. It is not an integral part of all possible key bindings. In i3 you can bind any key (even modifiers themselves) without any modifiers or with any combination of modifiers. <hr/> Similarly <code>bindsym</code> expects the same list of modifiers and not the key symbols of the modifiers. https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?comment=6355#comment-6355If you use that flag the action is executed on key up and not on key down.Mon, 27 Jul 2015 14:53:22 +0000https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?comment=6355#comment-6355Comment by serge poele for You can get the expected behaviour with <code>bindcode</code>: <pre><code>bindcode Mod1+23 workspace next bindcode Mod1+Shift+23 workspace prev </code></pre> <code>bindcode</code> expects a key code only for the last key, not the modifiers. As you noticed i3 stops parsing the keychain for <code>bindcode</code> when encountering the first key code. As per the <a href="http://i3wm.org/docs/userguide.html#keybindings">User's Guide</a> the syntax for the <code>bindcode</code> setting is <pre><code>bindcode [--release] [Modifiers+]keycode command </code></pre> Where <code>[Modifiers+]</code> is a optional (<code>+</code>-separated) list of any of these: <code>Mod1</code>, <code>Mod2</code>, <code>Mod3</code>, <code>Mod4</code>, <code>Mod5</code>, <code>Shift</code>, <code>Control</code> and <code>Mode_switch</code>. Not all of which may be defined for your keyboard layout (check with <code>xmodmap -pm</code>). <code>Mod1</code> commonly maps to Alt an <code>Mod4</code> to Super (aka Win-Key). <code>$mod</code> is just a variable (probably set to <code>Mod4</code> in your case) which i3 just replaces when parsing the configuration. It is not an integral part of all possible key bindings. In i3 you can bind any key (even modifiers themselves) without any modifiers or with any combination of modifiers. <hr/> Similarly <code>bindsym</code> expects the same list of modifiers and not the key symbols of the modifiers. https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?comment=6353#comment-6353Ah, I can upvote stuff now. :) Excellent.Mon, 27 Jul 2015 12:08:28 +0000https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?comment=6353#comment-6353Comment by serge poele for You can get the expected behaviour with <code>bindcode</code>: <pre><code>bindcode Mod1+23 workspace next bindcode Mod1+Shift+23 workspace prev </code></pre> <code>bindcode</code> expects a key code only for the last key, not the modifiers. As you noticed i3 stops parsing the keychain for <code>bindcode</code> when encountering the first key code. As per the <a href="http://i3wm.org/docs/userguide.html#keybindings">User's Guide</a> the syntax for the <code>bindcode</code> setting is <pre><code>bindcode [--release] [Modifiers+]keycode command </code></pre> Where <code>[Modifiers+]</code> is a optional (<code>+</code>-separated) list of any of these: <code>Mod1</code>, <code>Mod2</code>, <code>Mod3</code>, <code>Mod4</code>, <code>Mod5</code>, <code>Shift</code>, <code>Control</code> and <code>Mode_switch</code>. Not all of which may be defined for your keyboard layout (check with <code>xmodmap -pm</code>). <code>Mod1</code> commonly maps to Alt an <code>Mod4</code> to Super (aka Win-Key). <code>$mod</code> is just a variable (probably set to <code>Mod4</code> in your case) which i3 just replaces when parsing the configuration. It is not an integral part of all possible key bindings. In i3 you can bind any key (even modifiers themselves) without any modifiers or with any combination of modifiers. <hr/> Similarly <code>bindsym</code> expects the same list of modifiers and not the key symbols of the modifiers. https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?comment=6352#comment-6352@Adaephon. Thank you! This is very helpful although I am a little surprised with the behavior (that i3 only expects key code for the last key). However, I trust there is a reason for that. Can I ask this? What is [--release] in `bindcode` ? I understand the rest of it, but not that. Thank you.Mon, 27 Jul 2015 12:07:53 +0000https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?comment=6352#comment-6352Answer by analogbyte for Hi community, I have two small very related questions. A small legend (from xmodmap) for them: <pre><code>keycode 23 = Left Tab keycode 50 = Left Alt </code></pre> 1) Can I bind just alt+tab (without $mod) to <code>workspace next</code>? I currently have <code>bindcode $mod+23 workspace next</code>, which is fine, but I felt alt+tab is more natural. Can I do this without $mod? I tried <code>bindcode 23+50 workspace next</code>, but alt by itself switches workspaces if I do that. 2) The following bind does not work, I am not sure why: <code>bindcode $mod+50+23 workspace prev</code>. Well, it works: it binds $mod + shift, but not $mod +shift+tab. Thank you! https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?answer=6348#post-id-6348 You should avoid using bindcode when you can I guess, bindsym does most of the work for you. You should use these bindings for what you want: bindsym Mod1+Tab workspace next bindsym Mod1+Shift+Tab workspace prev Edit: Oh, and $mod is only set to Mod4 somewhere in your config. You could also change the $mod to Mod1 there, affecting all bindings.Sun, 26 Jul 2015 20:40:19 +0000https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?answer=6348#post-id-6348Comment by serge poele for You should avoid using bindcode when you can I guess, bindsym does most of the work for you. You should use these bindings for what you want: <pre><code>bindsym Mod1+Tab workspace next bindsym Mod1+Shift+Tab workspace prev </code></pre> Edit: Oh, and $mod is only set to Mod4 somewhere in your config. You could also change the $mod to Mod1 there, affecting all bindings. https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?comment=6349#comment-6349Thank you @analogbyte. This works well. I like using codes because when I change the layout to another language, I can't run some bindings. However, these are not affected during layout change, so you are right, this is better. Thank you! NOTE: I can't upvote the answer, but I would :).Sun, 26 Jul 2015 21:18:43 +0000https://faq.i3wm.org/question/6346/bind-alttab-to-workspace-next/?comment=6349#comment-6349