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, 2012Sun, 23 Aug 2015 20:56:44 +0000Conflict-safe bash and i3wm interoperability of ALT commandhttps://faq.i3wm.org/question/6490/conflict-safe-bash-and-i3wm-interoperability-of-alt-command/How to make it possible inside i3wm for `Alt` command to continue working as it should when in bash terminal? For example `Alt`+`Backspace` should be deleting the word, and `Alt`+`#` should be commenting the line, but because i3wm (default config) takes usage of `Alt` (`Mod1`) command as prefix for most of the commands how do you go around this? Do people solve this by using a combination of `Ctrl`+`Alt` as a basic replacement for `Mod1`? I am sure there's a simple solution to this problem I couldn't find :( Sat, 22 Aug 2015 16:34:03 +0000https://faq.i3wm.org/question/6490/conflict-safe-bash-and-i3wm-interoperability-of-alt-command/Answer by Airblader for How to make it possible inside i3wm for <code>Alt</code> command to continue working as it should when in bash terminal? For example <code>Alt</code>+<code>Backspace</code> should be deleting the word, and <code>Alt</code>+<code>#</code> should be commenting the line, but because i3wm (default config) takes usage of <code>Alt</code> (<code>Mod1</code>) command as prefix for most of the commands how do you go around this? Do people solve this by using a combination of <code>Ctrl</code>+<code>Alt</code> as a basic replacement for <code>Mod1</code>? I am sure there's a simple solution to this problem I couldn't find :( https://faq.i3wm.org/question/6490/conflict-safe-bash-and-i3wm-interoperability-of-alt-command/?answer=6491#post-id-6491 i3 will only grab the exact bindings that are configured. So Alt+Backspace should only be grabbed by i3 if there is actually a binding defined for it. Put that binding on something else and it should be available for your terminal again. However, I'd personally recommend using the Windows key as the modifier for i3. So many applications have shortcuts which typically work on Alt, you'll only run into more problems. Plus it sort of makes sense to have the "windows" key control your window manager. ;)Sat, 22 Aug 2015 21:26:14 +0000https://faq.i3wm.org/question/6490/conflict-safe-bash-and-i3wm-interoperability-of-alt-command/?answer=6491#post-id-6491Comment by Adaephon for i3 will only grab the exact bindings that are configured. So Alt+Backspace should only be grabbed by i3 if there is actually a binding defined for it. Put that binding on something else and it should be available for your terminal again. However, I'd personally recommend using the Windows key as the modifier for i3. So many applications have shortcuts which typically work on Alt, you'll only run into more problems. Plus it sort of makes sense to have the "windows" key control your window manager. ;) https://faq.i3wm.org/question/6490/conflict-safe-bash-and-i3wm-interoperability-of-alt-command/?comment=6495#comment-6495Alt was chosen as default in order to maximize compatibility, not because of its convenience. Meaning, Alt is actually on every keyboard but the Windows Keys might not be. It is easier to change the modifier key, if you can open any programs (for which you already need the modifier in i3)Sun, 23 Aug 2015 20:56:44 +0000https://faq.i3wm.org/question/6490/conflict-safe-bash-and-i3wm-interoperability-of-alt-command/?comment=6495#comment-6495Comment by milanaleksic for i3 will only grab the exact bindings that are configured. So Alt+Backspace should only be grabbed by i3 if there is actually a binding defined for it. Put that binding on something else and it should be available for your terminal again. However, I'd personally recommend using the Windows key as the modifier for i3. So many applications have shortcuts which typically work on Alt, you'll only run into more problems. Plus it sort of makes sense to have the "windows" key control your window manager. ;) https://faq.i3wm.org/question/6490/conflict-safe-bash-and-i3wm-interoperability-of-alt-command/?comment=6492#comment-6492OK, so that's the approach :) That said I would expect the nice people behind i3wm to recommend the windows button as the starting value for the action prefixSun, 23 Aug 2015 08:33:40 +0000https://faq.i3wm.org/question/6490/conflict-safe-bash-and-i3wm-interoperability-of-alt-command/?comment=6492#comment-6492