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

Feature request: allow some static workspace names #30

Open
eater opened this issue Apr 6, 2020 · 1 comment
Open

Feature request: allow some static workspace names #30

eater opened this issue Apr 6, 2020 · 1 comment

Comments

@eater
Copy link

eater commented Apr 6, 2020

I'd like to keep a few of my workspaces with names I give them, like "1: work", "4: pics", and use this daemon to dynamically name all the workspaces that aren't on that exceptions list, which I could configure in the config file. Possible?

@CastixGitHub
Copy link
Contributor

Hello, I just looked into this.
there is a single line to be changed, I changed it here
CastixGitHub@986ee65#diff-2f1824e92c1a5b4d944c82038f257be7R195
I noticed it reaching 100% coverage, writing this test
CastixGitHub@986ee65#diff-44c2c318351d9fcd29d696cbd1a4b0f0R135

so, you will also need to put something like this

bindsym $mod+i workspace i: work

in your i3 config file in order to create a named workspace
currently it this script does not take exceptions, it takes into consideration all numbered workspaces

so you can try to either use my fork (pytest branch), wait until this gets merged or fix the line yourself

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

No branches or pull requests

2 participants