i3 automatically start the same application in different workspaces
Multi tool use
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I would like to start lxterminal in both workspace 1 and workspace 2.
The end of ~/.config/i3/config file looks like this:
exec --no-startup-id i3-msg 'workspace 1; exec /usr/bin/lxterminal'
exec --no-startup-id i3-msg 'workspace 2; exec /usr/bin/lxterminal'
exec --no-startup-id i3-msg 'workspace 3; exec /usr/bin/firefox'
Resulting in opening 2 instances of lxterminal in workspace 1
window-manager i3
asked Oct 20 '17 at 19:41
xralf
1,8231865116
 |Â
show 1 more comment
up vote
0
down vote
favorite
I would like to start lxterminal in both workspace 1 and workspace 2.
The end of ~/.config/i3/config file looks like this:
exec --no-startup-id i3-msg 'workspace 1; exec /usr/bin/lxterminal'
exec --no-startup-id i3-msg 'workspace 2; exec /usr/bin/lxterminal'
exec --no-startup-id i3-msg 'workspace 3; exec /usr/bin/firefox'
Resulting in opening 2 instances of lxterminal in workspace 1
window-manager i3
asked Oct 20 '17 at 19:41
xralf
1,8231865116
1
You can use i3'sassignto make sure a window with some specific attributes always ends up on a specific workspace. I use this to make terminals appear on specific workspaces usingassign [instance="term1"] → 1and launch my terminal (st) with-c term1to have that particular instance show up on workspace 1. However, I don't know if you can assign an instance name like this with lxterminal. Maybe look into its profile features and how it affects X properties (usexpropto find these), or consider using another terminal if that's an option.
– Anonymouse
Oct 20 '17 at 20:20
I had a similar problem at some point, and solved it simply by gathering thei3-msgcommands, i.e.i3-msg 'workspace 1; exec /usr/bin/lxterminal; workspace 2; exec /usr/bin/lxterminal. I think this way of writing the commands will force i3 to execute them sequentially. Not sure this is actually the explanation or that it will work for you...
– Rastapopoulos
Oct 20 '17 at 22:17
@Rastapopoulos Could you please write it more precisely? I tried it exactly as you written it and it doesn't work.
– xralf
Oct 21 '17 at 15:05
I see that I forgot the final quote, but I guess that's not the error you encounter?
– Rastapopoulos
Oct 21 '17 at 22:13
@Rastapopoulos I haven't forgot the final quote.
– xralf
Oct 22 '17 at 8:57
 |Â
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I would like to start lxterminal in both workspace 1 and workspace 2.
The end of ~/.config/i3/config file looks like this:
exec --no-startup-id i3-msg 'workspace 1; exec /usr/bin/lxterminal'
exec --no-startup-id i3-msg 'workspace 2; exec /usr/bin/lxterminal'
exec --no-startup-id i3-msg 'workspace 3; exec /usr/bin/firefox'
Resulting in opening 2 instances of lxterminal in workspace 1
window-manager i3
asked Oct 20 '17 at 19:41
xralf
1,8231865116
I would like to start lxterminal in both workspace 1 and workspace 2.
The end of ~/.config/i3/config file looks like this:
exec --no-startup-id i3-msg 'workspace 1; exec /usr/bin/lxterminal'
exec --no-startup-id i3-msg 'workspace 2; exec /usr/bin/lxterminal'
exec --no-startup-id i3-msg 'workspace 3; exec /usr/bin/firefox'
Resulting in opening 2 instances of lxterminal in workspace 1
window-manager i3
asked Oct 20 '17 at 19:41
xralf
1,8231865116
edited Oct 20 '17 at 19:49
asked Oct 20 '17 at 19:41
xralf
1,8231865116
asked Oct 20 '17 at 19:41
xralf
1,8231865116
asked Oct 20 '17 at 19:41
xralf
1,8231865116
1,8231865116
1
You can use i3'sassignto make sure a window with some specific attributes always ends up on a specific workspace. I use this to make terminals appear on specific workspaces usingassign [instance="term1"] → 1and launch my terminal (st) with-c term1to have that particular instance show up on workspace 1. However, I don't know if you can assign an instance name like this with lxterminal. Maybe look into its profile features and how it affects X properties (usexpropto find these), or consider using another terminal if that's an option.
– Anonymouse
Oct 20 '17 at 20:20
I had a similar problem at some point, and solved it simply by gathering thei3-msgcommands, i.e.i3-msg 'workspace 1; exec /usr/bin/lxterminal; workspace 2; exec /usr/bin/lxterminal. I think this way of writing the commands will force i3 to execute them sequentially. Not sure this is actually the explanation or that it will work for you...
– Rastapopoulos
Oct 20 '17 at 22:17
@Rastapopoulos Could you please write it more precisely? I tried it exactly as you written it and it doesn't work.
– xralf
Oct 21 '17 at 15:05
I see that I forgot the final quote, but I guess that's not the error you encounter?
– Rastapopoulos
Oct 21 '17 at 22:13
@Rastapopoulos I haven't forgot the final quote.
– xralf
Oct 22 '17 at 8:57
 |Â
show 1 more comment
1
You can use i3'sassignto make sure a window with some specific attributes always ends up on a specific workspace. I use this to make terminals appear on specific workspaces usingassign [instance="term1"] → 1and launch my terminal (st) with-c term1to have that particular instance show up on workspace 1. However, I don't know if you can assign an instance name like this with lxterminal. Maybe look into its profile features and how it affects X properties (usexpropto find these), or consider using another terminal if that's an option.
– Anonymouse
Oct 20 '17 at 20:20
I had a similar problem at some point, and solved it simply by gathering thei3-msgcommands, i.e.i3-msg 'workspace 1; exec /usr/bin/lxterminal; workspace 2; exec /usr/bin/lxterminal. I think this way of writing the commands will force i3 to execute them sequentially. Not sure this is actually the explanation or that it will work for you...
– Rastapopoulos
Oct 20 '17 at 22:17
@Rastapopoulos Could you please write it more precisely? I tried it exactly as you written it and it doesn't work.
– xralf
Oct 21 '17 at 15:05
I see that I forgot the final quote, but I guess that's not the error you encounter?
– Rastapopoulos
Oct 21 '17 at 22:13
@Rastapopoulos I haven't forgot the final quote.
– xralf
Oct 22 '17 at 8:57
1
1
You can use i3's
assign to make sure a window with some specific attributes always ends up on a specific workspace. I use this to make terminals appear on specific workspaces using assign [instance="term1"] → 1 and launch my terminal (st) with -c term1 to have that particular instance show up on workspace 1. However, I don't know if you can assign an instance name like this with lxterminal. Maybe look into its profile features and how it affects X properties (use xprop to find these), or consider using another terminal if that's an option.– Anonymouse
Oct 20 '17 at 20:20
You can use i3's
assign to make sure a window with some specific attributes always ends up on a specific workspace. I use this to make terminals appear on specific workspaces using assign [instance="term1"] → 1 and launch my terminal (st) with -c term1 to have that particular instance show up on workspace 1. However, I don't know if you can assign an instance name like this with lxterminal. Maybe look into its profile features and how it affects X properties (use xprop to find these), or consider using another terminal if that's an option.– Anonymouse
Oct 20 '17 at 20:20
I had a similar problem at some point, and solved it simply by gathering the
i3-msg commands, i.e. i3-msg 'workspace 1; exec /usr/bin/lxterminal; workspace 2; exec /usr/bin/lxterminal. I think this way of writing the commands will force i3 to execute them sequentially. Not sure this is actually the explanation or that it will work for you...– Rastapopoulos
Oct 20 '17 at 22:17
I had a similar problem at some point, and solved it simply by gathering the
i3-msg commands, i.e. i3-msg 'workspace 1; exec /usr/bin/lxterminal; workspace 2; exec /usr/bin/lxterminal. I think this way of writing the commands will force i3 to execute them sequentially. Not sure this is actually the explanation or that it will work for you...– Rastapopoulos
Oct 20 '17 at 22:17
@Rastapopoulos Could you please write it more precisely? I tried it exactly as you written it and it doesn't work.
– xralf
Oct 21 '17 at 15:05
@Rastapopoulos Could you please write it more precisely? I tried it exactly as you written it and it doesn't work.
– xralf
Oct 21 '17 at 15:05
I see that I forgot the final quote, but I guess that's not the error you encounter?
– Rastapopoulos
Oct 21 '17 at 22:13
I see that I forgot the final quote, but I guess that's not the error you encounter?
– Rastapopoulos
Oct 21 '17 at 22:13
@Rastapopoulos I haven't forgot the final quote.
– xralf
Oct 22 '17 at 8:57
@Rastapopoulos I haven't forgot the final quote.
– xralf
Oct 22 '17 at 8:57
 |Â
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399422%2fi3-automatically-start-the-same-application-in-different-workspaces%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
You can use i3's
assignto make sure a window with some specific attributes always ends up on a specific workspace. I use this to make terminals appear on specific workspaces usingassign [instance="term1"] → 1and launch my terminal (st) with-c term1to have that particular instance show up on workspace 1. However, I don't know if you can assign an instance name like this with lxterminal. Maybe look into its profile features and how it affects X properties (usexpropto find these), or consider using another terminal if that's an option.– Anonymouse
Oct 20 '17 at 20:20
I had a similar problem at some point, and solved it simply by gathering the
i3-msgcommands, i.e.i3-msg 'workspace 1; exec /usr/bin/lxterminal; workspace 2; exec /usr/bin/lxterminal. I think this way of writing the commands will force i3 to execute them sequentially. Not sure this is actually the explanation or that it will work for you...– Rastapopoulos
Oct 20 '17 at 22:17
@Rastapopoulos Could you please write it more precisely? I tried it exactly as you written it and it doesn't work.
– xralf
Oct 21 '17 at 15:05
I see that I forgot the final quote, but I guess that's not the error you encounter?
– Rastapopoulos
Oct 21 '17 at 22:13
@Rastapopoulos I haven't forgot the final quote.
– xralf
Oct 22 '17 at 8:57