Hello. I’m a long time Linux user (mostly Ubuntu-based distros) and have recently hopped over to EndeavorOS i3WM edition. Took a little while getting used to not having a DE but I now love it. The problem I’m having is with keybindings and dedicated workspaces. When I enter $MOD+enter or $MOD+w, it opens either the terminal in WS1 or Firefox in WS2 and focuses on the correct workspace. When I enter $MOD+n to open the file manager (Thunar), it starts the program in WS3 but does not change focus to that workspace and I must then enter $MOD+3 to get to the file manager. I’ve looked through the i3 config file and everything looks correct.
I’m stumped and would appreciate any help on how I can automatically change focus to WS3 after opening Thunar using the keybinding.
Thanks but I already tried that. By the way, in my i3 config file, this is line 320, not 25. I uncommented this line and restarted i3wm. I then opened Firefox which changed focus to WS2. I then entered $MOD+n to open Thunar and it did not switch focus to WS3. I had to enter $MOD+3 to get to Thunar. I’d appreciate any other suggestions.
there must be something wrong with your i3wm config file
I’m on the EOS bspwm edition
and have just installed i3wm but not with EOS i3wm config
but have been on github and reviewed EOS i3wm config
everything is as it should be
The following lines have always been (uncommented) in my config file:
set $ws3 “3:”
assign [class=“Thunar”] $ws3
for_window [class=Thunar] focus
I have reloaded the config using mod+shift+c and then restarted i3 using mod+shift+r without resolution. I have also rebooted several times but I know that is unnecessary if i reload the config and restart i3.
At the suggestion of vlkon, I modified one of the lines as follows and it resolved the problem:
for_window [class=“Thunar”] move to workspace $ws3, focus
I appreciate that the forum helped solve the issue but I wonder why the default syntax doesn’t work for me but works for others?
Yeah, I’m confused why the slightly different syntax makes a difference. I also have EndeavorOS i3WM installed on my laptop at home and will see if I have the same problem on that system.
It doesn’t work for me neither. Well, sometimes. Perhaps it has something to do with Thunar version or the fact that Thunar wm_class is WM_CLASS(STRING) = "thunar", "Thunar" and i3wm is case sensitive.
could be related to the fact we are using i3-gaps… ?
And I know from firefox that it is changing class so it needs [class=(?i)firefox]
Could be checked with xprop command what should look like so: