-
Notifications
You must be signed in to change notification settings - Fork 237
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] change the refresh rate in-app #1104
Labels
feature
Requests for a new feature.
Comments
Already exists as a config field or a flag: https://clementtsang.github.io/bottom/0.8.0/configuration/config-file/flags/ As for on the fly, that sounds reasonable as a config screen thing whenever I get around to doing that (#159). |
ClementTsang
changed the title
[Feature] change the refresh rate
[Feature] change the refresh rate in-app
Apr 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Describe the feature request
I have searched through open and closed issue, pull requests, discussion, and have tried to find this in the documentation, but none of the keywords I used lead to any thread. But in case I have missed it, I apologize for creating a duplicate.
It would be nice to let the user change the refresh-rate (frequency of fetching information) on the fly and in the config. As for key bindings, I can suggest Ctrl+ for increase the frequency and Ctrl- for reducing it. It would be extra nice to see the current set frequency permanently or temporarily.
I have two reason for wanting to slow down the refresh rate:
btm
open on a side monitor but it constantly changing is a little bit too distracting. Would be nice if I can ask it to refresh once every 30 secs or somethingDesign consideration:
I don't know how long fetching all the info from the computer would take, but if it is something small, in the long run it can add up, so it would be nice if this time is subtracted from the wait time, so that all queries are almost perfectly at the same intervals. This is not necessary, by any means.
The text was updated successfully, but these errors were encountered: