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
I'm thinking, just have the window rule blocks inside a workspace "name" { block. (And, as a separate issue, a layout {} block too?)
workspace "name" {
layout {}
The alternative is match workspace="name", but this will cycle with open-on-workspace, which the solution above avoids.
match workspace="name"
open-on-workspace
Example use: having a "sensitive" workspace where all windows are blocked out from screencast: #1009
The text was updated successfully, but these errors were encountered:
To me the idea seems intuitive when writing out the window rules, and would make subsequent reviews of a config file straightforward.
Sorry, something went wrong.
No branches or pull requests
I'm thinking, just have the window rule blocks inside a
workspace "name" {
block. (And, as a separate issue, alayout {}
block too?)The alternative is
match workspace="name"
, but this will cycle withopen-on-workspace
, which the solution above avoids.Example use: having a "sensitive" workspace where all windows are blocked out from screencast: #1009
The text was updated successfully, but these errors were encountered: