Skip to content
New issue

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

Feat/Hyprland/Workspaces: Ignore workspaces #2568

Merged
merged 2 commits into from
Oct 12, 2023

Conversation

Syndelis
Copy link
Contributor

About this PR

This PR introduces a new option to hyprland/workspaces called ignore-workspaces. This option is an array of regexes that will be matched against workspace names. If there's a match, the workspace being created will not be shown on the user's bar.

Motivation

Chrome is notorious for launching a "sharing indicator" when your screen is being shared. This is specially frustrating when using tiling managers, such as Hyprland.

image

My current solution for not having to see it is by forcing it to move to a workspace named special:hell. This PR, then, lets me add it to a ignored list of workspaces, with the following rule:

"hyprland/workspaces": {
        "ignore-workspaces": [
            "(special:)?hell"
        ]
}

(note that I'm optionally matching against "special:" because Hyprland is not very consistent when it comes to naming special workspaces)

@Alexays
Copy link
Owner

Alexays commented Oct 12, 2023

LGTM, can you also update the GitHub wiki?
Thanks!

@Alexays Alexays merged commit a3774dc into Alexays:master Oct 12, 2023
6 of 8 checks passed
@Syndelis
Copy link
Contributor Author

Done!

@Syndelis Syndelis deleted the feat/hyprland-ignore-workspaces branch October 12, 2023 18:14
@Readf0x
Copy link

Readf0x commented Oct 20, 2023

I'm actually lmao right now. Naming the special workspace hell is absolute comedy gold. I am stealing that immediately lol. Thank you for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants