This repository has been archived by the owner on Sep 6, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey there,
I initially thank you for this fork. It allowed me to monitor my CPU flawlessly. This PR involves the changes I made locally to make use of the CLI program through Conky. I'm not a Conky expert, so I was not really sure whether the current version of CLI is directly usable with some Lua scripting. Instead of that, I went ahead with providing the following two options:
--output-once
. This simple flag allows the CLI program to finish immediately after printing the latest information about the CPU. I'm using it to update my Conky widget, however, it can be used by any such monitoring application.--refresh-in-place
. This is also a simple flag. It pops up anncurses
windows and flushes the information block. This might be useful for those who want to embed the terminal output into widgets. It requireslibncurses5-dev
to be installed as I added to README.This diff allowed me to monitor my 8-core Ryzen 7 5800H CPU in a very neat way 馃檪