https://faq.i3wm.org/questions/Frequently asked questions and answers about the i3 window managerenCopyright i3, 2012Thu, 17 Apr 2014 13:00:05 +0000https://faq.i3wm.org/question/3526/open-application-on-workspace-active-on-initialization/I want to launch an application on workspace 1, and then switch to a workspace 2, and have the app open in a container on workspace 1 in the background. If you try this, you will discover that the app launches in the workspace active when it _finishes_ loading rather than the workspace active on initialization. This occurs very frequently on my dual-screen system, where I want to open an app on one screen and then move to the other (which is also a different workspace) while it is opening. Does anyone have an idea how I might achieve this behavior?Sat, 15 Mar 2014 03:10:22 +0000https://faq.i3wm.org/question/3526/open-application-on-workspace-active-on-initialization/https://faq.i3wm.org/question/3526/open-application-on-workspace-active-on-initialization/?answer=3529#post-id-3529For applications that support it: ``--no-startup-id``. Have a look in the docs, or on the [FAQ](https://faq.i3wm.org/question/561/what-is-that-thing-called-no-startup-id/) for more details. Sat, 15 Mar 2014 07:23:17 +0000https://faq.i3wm.org/question/3526/open-application-on-workspace-active-on-initialization/?answer=3529#post-id-3529https://faq.i3wm.org/question/3526/open-application-on-workspace-active-on-initialization/?comment=3679#comment-3679Note that this flag does the _opposite_ of what the OP asked for. You _need_ startup ids to make i3 track where an application was launched. If that doesn’t work, probably the app does not support startup ids. Using --no-startup-id will definitely not fix it.Thu, 17 Apr 2014 13:00:05 +0000https://faq.i3wm.org/question/3526/open-application-on-workspace-active-on-initialization/?comment=3679#comment-3679