Closed Gigahawk closed 6 years ago
Does this also happen if you (I know this will sound silly) don't have any workspace number 1
binding of any sort in the config?
I think the issue here is that we extract workspaces from bindings also for "workspace number" bindings, but later on only check that the entire name doesn't yet exist. We should probably only extract "workspace" but not "workspace number" bindings and/or compare only the numbers rather than the name.
Of course this is ultimately subject to usage in a sense – we explicitly don't forbid using the same workspace number several times, so it's not exactly "broken". However, I'd make the argument that in the vast majority of cases people do not use the same number multiple times.
Actually, it looks like the issue was coming from the fact that I was running an older version of my config before I got around to switching all my workspace
bindings to workspace number
. Using the config as described above seems to work as expected.
I'm submitting a…
Current Behavior
I have scripts that monitor the currently active window and will rename the current workspace (I've switched all the related bindings in my config to use
workspace number
).When I plug in a monitor (or move the last workspace), a new workspace is created on that display with a number that already exists.
For example, if LVDS1 has a single workspace named
1 (Firefox Logo)
, plugging in a display to VGA1 and setting it to extend will create a workspace called1
, which renders one of the workspaces unusable.Expected Behavior
i3 should recognize that workspace 1 already exists and create a workspace with a different number or move an existing one over.
Reproduction Instructions
Plug in and a new display and set it to extend while having a custom named workspace
Environment
Output of
i3 --moreversion 2>&-
:update_workspaces:
update_workspace: