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

awesomewm: Setting to specify the prefix of the battery current and full charge path #13

Merged
merged 5 commits into from
Jan 28, 2015
Merged

Conversation

loathingKernel
Copy link
Contributor

In my case, the battery charge paths where named "charge_now" and "charge_full" rather than "energy_now" and "energy_full". This change enables the user to set their own prefix if it is needed.

@NuckChorris
Copy link
Owner

Great PR, though the behavior should probably match the behavior in C. I had kind of assumed it did, I guess I was wrong >_>

@loathingKernel
Copy link
Contributor Author

I agree completely that making it not require a setting is better. This commit matches more or less directly the way it is being done in the C code. Should I try to reduce code duplication while still having the same behavior or do you prefer it to be similar to the way it is done in C?

@NuckChorris
Copy link
Owner

Feel free to write it not idiomatically, Lua is certainly not C

@ghost
Copy link

ghost commented Jan 1, 2015

👍

NuckChorris added a commit that referenced this pull request Jan 28, 2015
awesomewm: Setting to specify the prefix of the battery current and full charge path
@NuckChorris NuckChorris merged commit 2ac2cba into NuckChorris:master Jan 28, 2015
@loathingKernel loathingKernel deleted the battery_path branch January 29, 2015 05:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants