Using one for_window and assign, or just for_window?
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
I want to both
- move my
irssi
window to a specific workspace - remove the border and title
Before I removed the border I had
assign [class="^kitty$" instance="^__irssi__"] → $ws10
This worked great, but now I want to remove the border so I add
for_window [class="^kitty$" instance="^__irssi__"] border none
That does exactly what I want, but I can drop the assign
and just have the for_window
with,
for_window [class="^kitty$" instance="^__irssi__"] move to workspace $ws10, border none
I know the i3 docs say this about for_window
,
The difference between
assign
andfor_window <criteria> move to workspace
is that the former will only be executed when the application maps the window (mapping means actually displaying it on the screen) but the latter will be executed whenever a window changes its properties to something that matches the specified criteria.
But that doesn't seem to provide me any guidance when I don't care about that. It also raises the question does anyone really care? It seems like assign
protects you against a window that both,
- Changes properties after initialization
- Would otherwise trigger a rule after one of those changes because you could not make the rule more specific to exclude the window's new properties?
Am I missing something here? I just have a feeling like that's a very small use case and I must be reading it wrong. Should I care about this difference? When would I care? And what should I do here, have an assign
and for_workspace
, or just merge them into a single for_workspace
?
configuration i3
add a comment |
up vote
-1
down vote
favorite
I want to both
- move my
irssi
window to a specific workspace - remove the border and title
Before I removed the border I had
assign [class="^kitty$" instance="^__irssi__"] → $ws10
This worked great, but now I want to remove the border so I add
for_window [class="^kitty$" instance="^__irssi__"] border none
That does exactly what I want, but I can drop the assign
and just have the for_window
with,
for_window [class="^kitty$" instance="^__irssi__"] move to workspace $ws10, border none
I know the i3 docs say this about for_window
,
The difference between
assign
andfor_window <criteria> move to workspace
is that the former will only be executed when the application maps the window (mapping means actually displaying it on the screen) but the latter will be executed whenever a window changes its properties to something that matches the specified criteria.
But that doesn't seem to provide me any guidance when I don't care about that. It also raises the question does anyone really care? It seems like assign
protects you against a window that both,
- Changes properties after initialization
- Would otherwise trigger a rule after one of those changes because you could not make the rule more specific to exclude the window's new properties?
Am I missing something here? I just have a feeling like that's a very small use case and I must be reading it wrong. Should I care about this difference? When would I care? And what should I do here, have an assign
and for_workspace
, or just merge them into a single for_workspace
?
configuration i3
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I want to both
- move my
irssi
window to a specific workspace - remove the border and title
Before I removed the border I had
assign [class="^kitty$" instance="^__irssi__"] → $ws10
This worked great, but now I want to remove the border so I add
for_window [class="^kitty$" instance="^__irssi__"] border none
That does exactly what I want, but I can drop the assign
and just have the for_window
with,
for_window [class="^kitty$" instance="^__irssi__"] move to workspace $ws10, border none
I know the i3 docs say this about for_window
,
The difference between
assign
andfor_window <criteria> move to workspace
is that the former will only be executed when the application maps the window (mapping means actually displaying it on the screen) but the latter will be executed whenever a window changes its properties to something that matches the specified criteria.
But that doesn't seem to provide me any guidance when I don't care about that. It also raises the question does anyone really care? It seems like assign
protects you against a window that both,
- Changes properties after initialization
- Would otherwise trigger a rule after one of those changes because you could not make the rule more specific to exclude the window's new properties?
Am I missing something here? I just have a feeling like that's a very small use case and I must be reading it wrong. Should I care about this difference? When would I care? And what should I do here, have an assign
and for_workspace
, or just merge them into a single for_workspace
?
configuration i3
I want to both
- move my
irssi
window to a specific workspace - remove the border and title
Before I removed the border I had
assign [class="^kitty$" instance="^__irssi__"] → $ws10
This worked great, but now I want to remove the border so I add
for_window [class="^kitty$" instance="^__irssi__"] border none
That does exactly what I want, but I can drop the assign
and just have the for_window
with,
for_window [class="^kitty$" instance="^__irssi__"] move to workspace $ws10, border none
I know the i3 docs say this about for_window
,
The difference between
assign
andfor_window <criteria> move to workspace
is that the former will only be executed when the application maps the window (mapping means actually displaying it on the screen) but the latter will be executed whenever a window changes its properties to something that matches the specified criteria.
But that doesn't seem to provide me any guidance when I don't care about that. It also raises the question does anyone really care? It seems like assign
protects you against a window that both,
- Changes properties after initialization
- Would otherwise trigger a rule after one of those changes because you could not make the rule more specific to exclude the window's new properties?
Am I missing something here? I just have a feeling like that's a very small use case and I must be reading it wrong. Should I care about this difference? When would I care? And what should I do here, have an assign
and for_workspace
, or just merge them into a single for_workspace
?
configuration i3
configuration i3
edited Nov 30 at 2:35
asked Nov 30 at 2:28
Evan Carroll
5,01994178
5,01994178
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485055%2fusing-one-for-window-and-assign-or-just-for-window%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown