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, 2012Thu, 17 Dec 2015 17:17:49 +0000Friendly names to workspaces don't work with "move container"https://faq.i3wm.org/question/7740/friendly-names-to-workspaces-dont-work-with-move-container/Note: there is a relevant question ("1657/add-friendly-name-to-workspace-but-keep-numbers-for-shortcuts") whose link I cannot post since I don't have enough karma. However, that question seems to address only the part about directly switching to a workspace, not moving a container to a workspace. I frequently rename my workspaces in an ad-hoc manner to easily see the names of the programs running in each workspace (and know where to switch). E.g. I have names like: "1: web, 2: code, 3: dbvis, 4: email" etc. These friendly names are prefixed with a number so that bindings like the following: # switch to workspace bindsym $mod+1 workspace number 1 bindsym $mod+2 workspace number 2 bindsym $mod+3 workspace number 3 ... do in fact work. What doesn't work however is bindings for the `move container to workspace` commands. E.g. the following don't work: # move focused container to workspace bindsym $mod+Shift+1 move container to workspace 1 bindsym $mod+Shift+2 move container to workspace 2 bindsym $mod+Shift+3 move container to workspace 3 Instead, when I press `$mod+Shift+1` a new workspace named "1" is created (alongside the already existing workspace "1: web") and the window is moved there. Thu, 17 Dec 2015 13:08:22 +0000https://faq.i3wm.org/question/7740/friendly-names-to-workspaces-dont-work-with-move-container/Answer by Airblader for Note: there is a relevant question ("1657/add-friendly-name-to-workspace-but-keep-numbers-for-shortcuts") whose link I cannot post since I don't have enough karma. However, that question seems to address only the part about directly switching to a workspace, not moving a container to a workspace. I frequently rename my workspaces in an ad-hoc manner to easily see the names of the programs running in each workspace (and know where to switch). E.g. I have names like: "1: web, 2: code, 3: dbvis, 4: email" etc. These friendly names are prefixed with a number so that bindings like the following: <pre><code># switch to workspace bindsym $mod+1 workspace number 1 bindsym $mod+2 workspace number 2 bindsym $mod+3 workspace number 3 </code></pre> ... do in fact work. What doesn't work however is bindings for the <code>move container to workspace</code> commands. E.g. the following don't work: <pre><code># move focused container to workspace bindsym $mod+Shift+1 move container to workspace 1 bindsym $mod+Shift+2 move container to workspace 2 bindsym $mod+Shift+3 move container to workspace 3 </code></pre> Instead, when I press <code>$mod+Shift+1</code> a new workspace named "1" is created (alongside the already existing workspace "1: web") and the window is moved there. https://faq.i3wm.org/question/7740/friendly-names-to-workspaces-dont-work-with-move-container/?answer=7742#post-id-7742Why would the syntax for moving be different from switching? Just use # move focused container to workspace bindsym $mod+Shift+1 move container to workspace number 1 bindsym $mod+Shift+2 move container to workspace number 2 bindsym $mod+Shift+3 move container to workspace number 3Thu, 17 Dec 2015 14:19:27 +0000https://faq.i3wm.org/question/7740/friendly-names-to-workspaces-dont-work-with-move-container/?answer=7742#post-id-7742Answer by basletic for Note: there is a relevant question ("1657/add-friendly-name-to-workspace-but-keep-numbers-for-shortcuts") whose link I cannot post since I don't have enough karma. However, that question seems to address only the part about directly switching to a workspace, not moving a container to a workspace. I frequently rename my workspaces in an ad-hoc manner to easily see the names of the programs running in each workspace (and know where to switch). E.g. I have names like: "1: web, 2: code, 3: dbvis, 4: email" etc. These friendly names are prefixed with a number so that bindings like the following: <pre><code># switch to workspace bindsym $mod+1 workspace number 1 bindsym $mod+2 workspace number 2 bindsym $mod+3 workspace number 3 </code></pre> ... do in fact work. What doesn't work however is bindings for the <code>move container to workspace</code> commands. E.g. the following don't work: <pre><code># move focused container to workspace bindsym $mod+Shift+1 move container to workspace 1 bindsym $mod+Shift+2 move container to workspace 2 bindsym $mod+Shift+3 move container to workspace 3 </code></pre> Instead, when I press <code>$mod+Shift+1</code> a new workspace named "1" is created (alongside the already existing workspace "1: web") and the window is moved there. https://faq.i3wm.org/question/7740/friendly-names-to-workspaces-dont-work-with-move-container/?answer=7744#post-id-7744This works as expected: # switch to workspace bindsym $mod+1 workspace number 1: web bindsym $mod+2 workspace number 2: code # move focused container to workspace bindsym $mod+Shift+1 move container to workspace 1: web bindsym $mod+Shift+2 move container to workspace 2: code; workspace 2: code Note that `$mod+Shift+2` will both move container to workspace 2 and go to workspace 2.Thu, 17 Dec 2015 14:42:30 +0000https://faq.i3wm.org/question/7740/friendly-names-to-workspaces-dont-work-with-move-container/?answer=7744#post-id-7744Comment by basletic for This works as expected: <pre><code># switch to workspace bindsym $mod+1 workspace number 1: web bindsym $mod+2 workspace number 2: code # move focused container to workspace bindsym $mod+Shift+1 move container to workspace 1: web bindsym $mod+Shift+2 move container to workspace 2: code; workspace 2: code </code></pre> Note that <code>$mod+Shift+2</code> will both move container to workspace 2 and go to workspace 2. https://faq.i3wm.org/question/7740/friendly-names-to-workspaces-dont-work-with-move-container/?comment=7746#comment-7746@Airblader Indeed, it might not work in dynamical 'scenario'.Thu, 17 Dec 2015 17:17:49 +0000https://faq.i3wm.org/question/7740/friendly-names-to-workspaces-dont-work-with-move-container/?comment=7746#comment-7746Comment by Airblader for This works as expected: <pre><code># switch to workspace bindsym $mod+1 workspace number 1: web bindsym $mod+2 workspace number 2: code # move focused container to workspace bindsym $mod+Shift+1 move container to workspace 1: web bindsym $mod+Shift+2 move container to workspace 2: code; workspace 2: code </code></pre> Note that <code>$mod+Shift+2</code> will both move container to workspace 2 and go to workspace 2. https://faq.i3wm.org/question/7740/friendly-names-to-workspaces-dont-work-with-move-container/?comment=7745#comment-7745This won't work with dynamically renamed workspaces, though.Thu, 17 Dec 2015 16:21:16 +0000https://faq.i3wm.org/question/7740/friendly-names-to-workspaces-dont-work-with-move-container/?comment=7745#comment-7745