-
-
Notifications
You must be signed in to change notification settings - Fork 960
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
acpi should take precedence in battery #541
Conversation
Co-authored-by: Maxim Baz <git@maximbaz.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Snuggle for PR.
It might be better if we swap order between acpi
and upower
, and leave pmset
as it is. Like pmset
→ acpi
→ upower
. Looks like you missed the variable used in conditional.
This needs testing 🛠️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't locally tested this, But code look good 👍
In the meantime, could I please ask for some documentation on how to actually locally run your tests? I just get some |
😆 We depend on kward/shunit2 for testing as submodule.
After that |
Any progress on this? I'd like to merge this. |
@denysdovhan — Just waiting for a second person to test & review, I believe. |
@Snuggle good. I'm merging this. P.S: I'll be grateful for a PR with some tests for battery section. |
Description
Shuffled battery section around, should fix issue #526. acpi seems to give a nicer output than upower and doesn't give a bunch of extra battery/peripheral devices that are hard to filter. If acpi returns 0% charge, the device is likely a desktop without a battery.
Changes haven't been tested yet, testing yourself would be appreciated!
Fix #526