Option to disable config live-reloading #219
HardGraphite
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
I mean I guess I could add a flag to disable it, I'm just not sure when 500 ms metadata polling could be this big of a problem. |
Beta Was this translation helpful? Give feedback.
1 reply
-
The thing about cost here is that niri always runs and refreshes/polls one way or another, where e.g. alacritty could be obscured thus suspended and never receive events. So it's the same as why kernel polls input devices, etc. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The config live-reloading feature is nice for debugging and exploring. However, I'm afraid it is not very useful for daily use, especially considering that it is implemented by polling the file metadata every 500 ms.
Is it a good idea to add an option allowing user to disable this feature? Maybe it can be called
live_config_reload
, just like what is done in Alacritty.Beta Was this translation helpful? Give feedback.
All reactions