We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I reboot the PC, the locked containers are forgotten and I need to play with the hotkeys again.
Can there be a way to set some setting in i3 config, or someplace else, where I define that "deadbeef, thunderbird, qownnotes" to be always locked?
Similarly how I can in i3 config set which applications belong to which workspace by using their wm_class. assign [class="Thunderbird"] $WS0
assign [class="Thunderbird"] $WS0
or assigning which programs are floating
for_window [class="plank"] floating enable
I dont do this things on the fly, I set it once in config and they are done, that should be possible here too.
thanks
The text was updated successfully, but these errors were encountered:
@DoTheEvo, not sure if you are still facing this issue.
I believe something like this should work for_window [class="plank"] exec "i3-persist lock", floating enable
for_window [class="plank"] exec "i3-persist lock", floating enable
Sorry, something went wrong.
No branches or pull requests
When I reboot the PC, the locked containers are forgotten and I need to play with the hotkeys again.
Can there be a way to set some setting in i3 config, or someplace else, where I define that "deadbeef, thunderbird, qownnotes" to be always locked?
Similarly how I can in i3 config set which applications belong to which workspace by using their wm_class.
assign [class="Thunderbird"] $WS0
or assigning which programs are floating
for_window [class="plank"] floating enable
I dont do this things on the fly, I set it once in config and they are done, that should be possible here too.
thanks
The text was updated successfully, but these errors were encountered: