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

Don't run multiple instances when calling xidlehook again #36

Open
Shourai opened this issue Mar 11, 2020 · 1 comment
Open

Don't run multiple instances when calling xidlehook again #36

Shourai opened this issue Mar 11, 2020 · 1 comment

Comments

@Shourai
Copy link

Shourai commented Mar 11, 2020

Since it is possible to append multiple --timers.
Would it be possible to add a way for it to detect if there is already an instance
of xidlehook running and if it is don't run another instance?

For example, if I run picom -b twice, it detects than another instance is already running
and does nothing.

Sometimes I have to reload my window manager and in the startup script of the window
manager it also starts up xidlehook.
To mitigate this I wrote a simple if-statement to check if it is already running.
But it would preferable if the program checked it instead.

@ghost
Copy link

ghost commented Oct 30, 2022

You can mitigate this easily. Let's say you run i3. Each time you re-login, xidlehook instances increase.
You can fix this easily by killing xidlehook the moment you exit i3.
bindsym <key> exec --no-startup-id pkill xdlehook | i3-msg exit

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

1 participant