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

Reloads only once every two config saves under --reload #881

Closed
alexozer opened this Issue Dec 3, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@alexozer

alexozer commented Dec 3, 2017

Dotfiles and config.

When running polybar with polybar top --reload, the bar only restarts once every two times I save the config file, not every time I save it.

@alexozer alexozer changed the title from Reloads only once every two config save under --reload to Reloads only once every two config saves under --reload Dec 3, 2017

@patrick96

This comment has been minimized.

Show comment
Hide comment
@patrick96

patrick96 Dec 3, 2017

Collaborator

Is this behaviour consistent?
Can you run polybar with -l info and post the whole output as well as how many times you saved the config file.

Collaborator

patrick96 commented Dec 3, 2017

Is this behaviour consistent?
Can you run polybar with -l info and post the whole output as well as how many times you saved the config file.

@NBonaparte

This comment has been minimized.

Show comment
Hide comment
@NBonaparte

NBonaparte Dec 3, 2017

Collaborator

Does the same thing happen when you send SIGUSR1 to polybar, i.e. pkill -USR1 polybar? This should work independently of the -r flag.

Collaborator

NBonaparte commented Dec 3, 2017

Does the same thing happen when you send SIGUSR1 to polybar, i.e. pkill -USR1 polybar? This should work independently of the -r flag.

@patrick96

This comment has been minimized.

Show comment
Hide comment
@patrick96

patrick96 Feb 25, 2018

Collaborator

Closing due to inactivity

Collaborator

patrick96 commented Feb 25, 2018

Closing due to inactivity

@patrick96 patrick96 closed this Feb 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment