Polybar via dot now uses environment variables to define which monitors are left, right, and middle. The i3 configuration hard codes these. The result is, after updating monitor positions, or working on multiple machines with different monitor setups, workspaces open on the wrong monitor. I3 should use the same environment variables that dot polybar sets. If it doesn't reload in the config file, dot polybar should signal i3 to update. i3 should pick up those env vars at boot as well. This could be tricky, as it's not yet supported by dot polybar to pass/set it's environment to be read by other proceses.
Perhaps dot could bootstrap i3, instead of the other way around.
Polybar via dot now uses environment variables to define which monitors are left, right, and middle. The i3 configuration hard codes these. The result is, after updating monitor positions, or working on multiple machines with different monitor setups, workspaces open on the wrong monitor. I3 should use the same environment variables that dot polybar sets. If it doesn't reload in the config file, dot polybar should signal i3 to update. i3 should pick up those env vars at boot as well. This could be tricky, as it's not yet supported by dot polybar to pass/set it's environment to be read by other proceses.
Perhaps dot could bootstrap i3, instead of the other way around.