i3 FAQ - Individual question feed

i3-msg set workspace on specific output

Wed, 06 Aug 2014 05:31:56 +0000

So I am trying to dynamically set my workspaces to output on specific displays. The problem is i3-msg doesn't seem to want to accept `i3-msg workspace 1 output $PRIMARY`. It works perfectly fine in my ~/.i3/config but when I run it in i3-msg it creates a brand new workspace with the name "1 output HDMI-0" instead of forcing workspace 1 to output HDMI-0. I've also tried putting quotes around the workspace name to no avail `i3-msg workspace "1" output $PRIMARY`. I would really appreciate it if someone could point me in the right direction, thanks!

Answer by Adaephon for
So I am trying to dynamically set my workspaces to output on specific displays. The problem is i3-msg doesn't seem to want to accept `i3-msg workspace 1 output $PRIMARY`. It works perfectly fine in my ~/.i3/config but when I run it in i3-msg it creates a brand new workspace with the name "1 output HDMI-0" instead of forcing workspace 1 to output HDMI-0. I've also tried putting quotes around the workspace name to no avail `i3-msg workspace "1" output $PRIMARY`. I would really appreciate it if someone could point me in the right direction, thanks!

Wed, 06 Aug 2014 11:50:21 +0000

There is a difference between the `workspace` *command* and the `workspace` *setting*. They have the same name but do different things: - The `workspace` *setting* (`workspace output `) in the configuration file sets specific outputs for workspaces. It can not be used as a command. (`i3-msg` only accepts commands) - Whereas the `workspace` *command* (usage `workspace `) switches to the given workspace, creating it, if it does not yet exist. It cannot be used to set or even move a workspace to another output `i3-msg` only accepts commands, so when you tell it `workspace 1 output HDMI-0` it expects the `workspace` *command* and takes everything after it as the name of the new workspace. ---- Setting an output for a workspace *before* it is created can only be done in the configuration file. Any workspace not set there will open on the current output. You can always move workspaces *after* they have been created using the `move` command in the form `move to `. Where `` is any direction or the name of the output (as used with the `workspace` *setting*).

Comment by geekingreen for
There is a difference between the `workspace` command and the `workspace` setting. They have the same name but do different things:

The `workspace` setting (`workspace <workspace> output <output>`) in the configuration file sets specific outputs for workspaces. It can not be used as a command. (`i3-msg` only accepts commands)

Whereas the `workspace` command (usage `workspace <workspace>`) switches to the given workspace, creating it, if it does not yet exist. It cannot be used to set or even move a workspace to another output

`i3-msg` only accepts commands, so when you tell it `workspace 1 output HDMI-0` it expects the `workspace` command and takes everything after it as the name of the new workspace.

Setting an output for a workspace before it is created can only be done in the configuration file. Any workspace not set there will open on the current output.

You can always move workspaces after they have been created using the `move` command in the form `move <workspace> to <output>`. Where `<output>` is any direction or the name of the output (as used with the `workspace` setting).

Wed, 06 Aug 2014 16:20:39 +0000

Here is the real problem, I have several machines that I sync my dotfiles across. Each machine has different displays with different names M1: HDMI-0, DVI-D-0 M2: DP-2, DP-3, I can use xrandr to query which is primary or secondary. I want to use what I get from that query to set my workspace outputs

Comment by geekingreen for
There is a difference between the `workspace` command and the `workspace` setting. They have the same name but do different things:

The `workspace` setting (`workspace <workspace> output <output>`) in the configuration file sets specific outputs for workspaces. It can not be used as a command. (`i3-msg` only accepts commands)

Whereas the `workspace` command (usage `workspace <workspace>`) switches to the given workspace, creating it, if it does not yet exist. It cannot be used to set or even move a workspace to another output

`i3-msg` only accepts commands, so when you tell it `workspace 1 output HDMI-0` it expects the `workspace` command and takes everything after it as the name of the new workspace.

Setting an output for a workspace before it is created can only be done in the configuration file. Any workspace not set there will open on the current output.

You can always move workspaces after they have been created using the `move` command in the form `move <workspace> to <output>`. Where `<output>` is any direction or the name of the output (as used with the `workspace` setting).

Wed, 06 Aug 2014 15:44:00 +0000

That explains it. Is there a way to dynamically set a variable in the i3 config? Moving a workspace won't work since none of them will have any containers on them at the time I'd want to move them, causing them to spawn on whatever display is active at the time when I switch to that workspace.

Comment by ANOKNUSA for
There is a difference between the `workspace` command and the `workspace` setting. They have the same name but do different things:

The `workspace` setting (`workspace <workspace> output <output>`) in the configuration file sets specific outputs for workspaces. It can not be used as a command. (`i3-msg` only accepts commands)

Whereas the `workspace` command (usage `workspace <workspace>`) switches to the given workspace, creating it, if it does not yet exist. It cannot be used to set or even move a workspace to another output

`i3-msg` only accepts commands, so when you tell it `workspace 1 output HDMI-0` it expects the `workspace` command and takes everything after it as the name of the new workspace.

Setting an output for a workspace before it is created can only be done in the configuration file. Any workspace not set there will open on the current output.

You can always move workspaces after they have been created using the `move` command in the form `move <workspace> to <output>`. Where `<output>` is any direction or the name of the output (as used with the `workspace` setting).

Wed, 06 Aug 2014 16:11:26 +0000

i3 loads the entire configuration at start-up; any changes to variables in the configuration file would require you to restart the window manager afterward. You should explain exactly why you want to do this; it seems [almost random from where I'm sitting.](http://xyproblem.info)

Comment by Adaephon for
There is a difference between the `workspace` command and the `workspace` setting. They have the same name but do different things:

The `workspace` setting (`workspace <workspace> output <output>`) in the configuration file sets specific outputs for workspaces. It can not be used as a command. (`i3-msg` only accepts commands)

Whereas the `workspace` command (usage `workspace <workspace>`) switches to the given workspace, creating it, if it does not yet exist. It cannot be used to set or even move a workspace to another output

`i3-msg` only accepts commands, so when you tell it `workspace 1 output HDMI-0` it expects the `workspace` command and takes everything after it as the name of the new workspace.

Setting an output for a workspace before it is created can only be done in the configuration file. Any workspace not set there will open on the current output.

You can always move workspaces after they have been created using the `move` command in the form `move <workspace> to <output>`. Where `<output>` is any direction or the name of the output (as used with the `workspace` setting).

Wed, 06 Aug 2014 20:37:14 +0000

You could just write a script, which does the appropriate replacements right after the syncing. Depending on the mechanism you use for syncing it could be easily automated.