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.

Sign up for GitHub

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

Jump to bottom

Reload blocks on signal #37

Open
domsson opened this issue Jul 2, 2020 · 1 comment
Open

Reload blocks on signal #37

domsson opened this issue Jul 2, 2020 · 1 comment
Assignees
@domsson
Labels
enhancement New feature or request

Comments

@domsson
Copy link
Owner

domsson commented Jul 2, 2020

Other projects, like i3blocks and lemonblocks, offer the option to send a signal to request reloading of a certain block/module. It shouldn't be too hard to implement this in succade, so let's look into it.

In the config, blocks could then have a new option, signal, which could be assigned a signal number. When succade receives a user signal, it can check which block it matches and mark that block as "due". If the block is a live block, we should ignore the signal option with one exception: if the live block has died, we should restart it if there is a signal coming in.
@domsson domsson added the enhancement New feature or request label Jul 2, 2020
@domsson domsson self-assigned this Jul 2, 2020
@domsson
Copy link
Owner Author

domsson commented Nov 5, 2020

Actually, this requires more changes to the code than I had originally anticipated, so I'm currently thinking to not implement this feature after all.

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

@domsson domsson

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@domsson