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.

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

Goes orange when battery at 100% and connected #1

Open
dieggsy opened this issue Jul 10, 2016 · 12 comments
Open

Goes orange when battery at 100% and connected #1

dieggsy opened this issue Jul 10, 2016 · 12 comments
Labels

Comments

@dieggsy
Copy link

dieggsy commented Jul 10, 2016

Not sure if this is intended behavior, but for me, the color of the battery percentage is green as it's charging, but switches to orange when it's at 100% and is connected (which implies it's discharging, which isn't the case).

@swsnr
Copy link
Contributor

swsnr commented Jul 10, 2016

It's not intended behaviour for sure but I can't make anything from this scant report. Please add relevant information, including your OS, your Emacs version, etc.

@dieggsy
Copy link
Author

dieggsy commented Jul 10, 2016

Yep, sorry about that.

OS: OSX El Capitan 10.11.5
Emacs: Emacs version 24.5.1, running from osx terminal.
Additionally running smart-mode-line.
Installed fancy battery through elpa (M-x package-install fancy-battery)

Please let me know what else you might need.

@swsnr
Copy link
Contributor

swsnr commented Jul 11, 2016

Ok, the problem is that we don't check whether AC is plugged. We just check whether it's charging, and that's not the case anymore when the battery is fully charged.

We need to change fancy-battery-default-mode-line to extract ?L from fancy-battery-last-status, and check whether it's "AC". In that case we still need to consider the battery as "charging" and apply the charging face.

@therockmandolinist Would you like to try and open a corresponding pull request?

@swsnr swsnr added the bug label Jul 11, 2016
@dieggsy
Copy link
Author

dieggsy commented Jul 11, 2016

@lunaryorn I'm afraid I'm not much of an emacs-lisp coder at all, so my helpfulness there would be extremely limited if at all existent.

@swsnr
Copy link
Contributor

swsnr commented Jul 11, 2016

@therockmandolinist This change would be easy enough; it'd be nice opportunity to learn Emacs Lisp.

If you'd like to learn I could help you and guide you through the change 😊

@dieggsy
Copy link
Author

dieggsy commented Jul 12, 2016

I also am not proficient in any way at using github, so there's also that, but I'd be glad to learn emacs lisp if you think it would be worthwhile.

@swsnr
Copy link
Contributor

swsnr commented Jul 12, 2016

@therockmandolinist Well I'd help you with Github as well, but the question is whether you'd like to give it a shot 😊 We can do this together 👍

@swsnr
Copy link
Contributor

swsnr commented Jul 12, 2016

@therockmandolinist That said it's totally fine if you don't want to 😊 I'll fix the issue myself at some point then.

@dieggsy
Copy link
Author

dieggsy commented Jul 13, 2016

@lunaryorn I have a feeling it'd be better that way, but I do appreciate the encouragement.

@swsnr
Copy link
Contributor

swsnr commented Jul 13, 2016

@therockmandolinist Alright, I'll fix it myself then; please be patient, though, I've been relocating recently and am quite busy currently so it'll take me a while to push a fix.

@dieggsy
Copy link
Author

dieggsy commented Jul 13, 2016

@lunaryorn Absolutely, no rush here. Thanks!

@swsnr swsnr self-assigned this Aug 18, 2016
@swsnr
Copy link
Contributor

swsnr commented Oct 31, 2016

@therockmandolinist So, to be honest, I won't fix this. I'm not using this package anymore myself, and have no motivation to work on it anymore.

I'm sorry but if you don't fix it yourself, you'll have to live with the bug now.

@swsnr swsnr removed their assignment May 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants