You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assign tabbed layout for certain programs then opening one in a workspace. Let say Firefox in Workspace 2
assign [class=Firefox*|Thunderbird] 2
for_window [class=Firefox*|Thunberbird] layout tabbed
#minimal config as in readme
bindsym $mod+1 workspace number 1
bindsym $mod+2 workspace number 2
bindsym $mod+Shift+1 move container to workspace number 1
bindsym $mod+Shift+2 move container to workspace number 2
Open new window for ex. Firefox History oder Firefox Bookmark or Thunderbird in Workspace 2
Each time it will spawn new workspace for each window. That is bad, that I must use mouse to switch between them.
Expected behaviour is all windows should spawn in the same workspace.
I'm using ubuntu 16.04 KDE , i3 version 4.17.1 (also same problem in i3 version 4.11) with dual monitor.
The text was updated successfully, but these errors were encountered:
It's actually an issue with your i3 config file and it is related to assign, not to the tabbed layout:
You need to replace: assign [class=Firefox*|Thunderbird] 2
with: assign [class=Firefox*|Thunderbird] number 2
Wow, thank you so much! What an idiot I am, writing down without noticing it.
Then we let the maintainer close this issue when README, Wiki or FAQ are more clear about it.
Until then I would change the subject so other with same problem can find easier.
iiey
changed the title
Problem opening new window in tabbed layout always create new workspace
Doc need: windows opened in multiple workspaces cause by false config
Jun 19, 2020
Step to reproduce:
Each time it will spawn new workspace for each window. That is bad, that I must use mouse to switch between them.
Expected behaviour is all windows should spawn in the same workspace.
I'm using ubuntu 16.04 KDE , i3 version 4.17.1 (also same problem in i3 version 4.11) with dual monitor.
The text was updated successfully, but these errors were encountered: