Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't move specific workspace to another output #3704

dyc3 opened this issue May 19, 2019 · 1 comment


None yet
3 participants
Copy link

commented May 19, 2019

I'm submitting a…

[x] Bug
[x] Feature Request
[ ] Documentation Request
[ ] Other (Please describe in detail)

Current Behavior

When the command i3-msg "move workspace 2 to output primary" is run, the currently active window is moved to a new workspace called 2 to output primary

Expected Behavior

Expected workspace 2 to be moved to the specified primary output

Reproduction Instructions

  1. Open a terminal
  2. Run i3-msg "move workspace 2 to output primary"


Output of i3 --moreversion 2>&-:

Binary i3 version:  4.16.1-1-g341fcf9 (2019-01-27, branch "gaps") © 2009 Michael Stapelberg and contributors
Running i3 version: 4.16.1-1-g341fcf9 (2019-01-27, branch "gaps") (pid 2548)
Loaded i3 config: /home/carson/.config/i3/config (Last modified: Sun 19 May 2019 01:18:00 PM EDT, 306 seconds ago)

The i3 binary you just called: /usr/local/bin/i3
The i3 binary you are running: i3

Logfile URL:
- Linux Distribution & Version: Ubuntu 18.04
- Are you using a compositor (e.g., xcompmgr or compton): compton

@i3bot i3bot added the enhancement label May 19, 2019


This comment has been minimized.

Copy link

commented May 19, 2019

You tagged this both as bug and feature request, I'm not quite sure what to make of it. There is no command to name a workspace to be moved to another output, it only works for the focused workspace. If the workspace isn't empty, you can use command criteria to match on the workspace:

[workspace=...] move workspace to output primary

As far as adding syntax to move a workspace by name goes, I'm 99% sure we have an open issue for it already, but I'll leave this one open until we can link to it (can't search for it right now).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.