bat shit

[wuxmedia]

So -

• Bash was annoying me, time to fuck it up a bit.
• Wanted to see if bat was charging or not as well as capacity.
• Bored.

Code: Select all

#!/bin/bash

# bat.sh
# Queries /sys/class/power_supply/BATn/ things
# and makes it a pretty ascii output.

if [ -d /sys/class/power_supply/BAT0/ ]
then 
DIR=/sys/class/power_supply/BAT0/
else
DIR=/sys/class/power_supply/BAT1
fi

CAP=$(cat $DIR/capacity)
STATE=$(cat $DIR/status)
# Charging or What??
if [[ $STATE  == D* ]]
then ST="-"
else ST="+"
fi

if [[ $CAP == 100 ]]
then ST=""
fi
	echo {$CAP$ST]

- Of course the formatting is in this last line.
very handy piped to i3 bar thing.
Which - for my ref, looks like this:

Code: Select all

#!/bin/sh
# shell script to prepend i3status with more stuff

i3status | while :
 do
  read line
  echo "$(mocp -Q %title) | $( ~/bin/./bat.sh) | $line" || exit 1
 done

outputs something like:

Code: Select all

{98+]

and well, when it's 100% it's full, so shows neither charge or discharge. Which while absolutely floating my boat (as the char width remains the same, how sad am I?) User - as always can season as they wish. prolly pipe it to conky if wished ;)

[dkeg]

Nice. I have the same in my bar script. Very cool that you and I have the same output with a slightly different script. You were very complete by adding the checks. Nice job. I do a double ++ when full. My rendition is sourced in my latest scrot. Here's the relevant piece

Code: Select all

batt() {
     level=$(cat /sys/class/power_supply/BAT0/capacity 2>/dev/null)
     if [ $level -lt '25' ]; then
         echo %{+u}$red$level%{-u}
     else
         echo $green$level
     fi
       }

battstate() {
    state=$(cat /sys/class/power_supply/BAT0/status)
    case $state in 
        "Charging")
            echo $green2+ ;; 
        "Discharging")
            echo $red- ;;
        "Full")
            echo $green2++$none ;;
    esac
        }

[wuxmedia]

ugh, /me is a Johnny come lately uh-gain :(

I like the case, much less obfuscated than the "D*" test.
I think that was the tldp.org "test" page when I googled that test idea.
Err. where do you put your functions?

Nice idea with the colours, not sure if i3bar will let me.
Are you still rocking your "plugin or die fuckker" dunst script? was thinking of adapting that to go with this.
It is rare that I miss the fact it's charging or not.

Hell, we'll end up with that xfce powerman icons soon, or maybe not :)

[dkeg]

Its part of my status bar script. Yeah still have a separate notification script for that. Use bar instead of dunst.

[wuxmedia]

gotcha.

[rhowaldt]

no matter whether 2 men invent the wheel separately; there's still a wheel.
cool script Wux, nice and simple. Drew's looks good as well, but i personally prefer the text-only approach. seeing how Drew is our colourguy, it makes total sense for him to use colours :)

thanks for sharing!

[wuxmedia]

Only because you mention it and I've been listening to THHG2G all weekend, or anytime in the car:
Not any kind of comment, just thought it's funny, and if you haven't seen the whole series, you must:
http://youtu.be/zBmdkhDGZ8A?t=25m33s
shared from appropriate time index :)
Share and Enjoy :)

[rhowaldt]

^ cool, i needed that :) thanks!

[stark]

Thanks wux and dkeg! Boy I am stupid for using the plain version with pidsley's color-echo method.

[dkeg]

well, displaying info; its just a matter of
1. locate
2. capture
2. filter [sed,awk,cut]
4. dispaly [bar,conky,osd,tmux,etc]
5. bloat it up (optional)

[rhowaldt]

^ that seems completely rational to me. some people might call this "obvious", but i always like it when somebody analyses obvious things, lest we forget how they work and take them for granted. thanks!

[dkeg]

Cool thanks. And +1 for using 'lest' .

[wuxmedia]

before, I was using acpi -b (manipulate) then I remembered it's all in /sys/blah/
all sorts of fun things in files linux.

Code: Select all

cat /proc/loadavg 

[stark]

^ whats the case for bsdland ?

[wuxmedia]

Too insecure for BSD :p
Bones might know, if google doesn't?

[stark]

I have the temptation to install OpenBSD in the *cough* #! *cough* partition as I don't boot into it that much but I have no idea if the Bsd bootloaders are multi-boot friendly and can I mentally handle the constant switch between GNU and BSD userland ?

[pidsley]

I'm have the temptation to install OpenBSD in the *cough* #! *cough* partition as I don't boot into it that much but I have no idea if the Bsd bootloaders are multi-bootfriendly and can I mentally handle the constant switch between GNU and BSD userland ?

Please don't try this. BSDs are not friendly about sharing a disk with other operating systems. I'm sure it can be done, but I don't think it's easy.

[stark]

^ Thanks pidsley! Seriously Noted.

[pidsley]

^ bones may have a different opinion, but every time I use a BSD I install it on a test machine and give it the entire disk. It just makes my life easier.

And yes, at least for me, the switch between Linux userland and BSD can be a bit challenging. I'm sure I could get used to BSD if I used it all the time (and I have considered it) but it's confusing at first.

[bones]

^ Agreed, I only ever give it the entire disk. Haven't even attempted otherwise.

As for battery monitoring, there's options. I often go the lazy route and just use xfce-battery (NOT xfce-powermanager). acpi works, too. And there's stuff like this, that I haven't tried:

http://www.nongnu.org/gap/batmon/

EDIT: Oh yes, forgot I wrote a tutorial for myself on this:

Battery monitoring in OpenBSD:

Get a list of sensors:

Code: Select all

user@openbsd:~$ sysctl hw.sensors

Code: Select all

hw.sensors.acpibat0.watthour0=4.35 Wh (last full capacity)
hw.sensors.acpibat0.watthour1=0.43 Wh (warning capacity)
hw.sensors.acpibat0.watthour2=0.00 Wh (low capacity)
hw.sensors.acpibat0.watthour3=3.24 Wh (remaining capacity), OK
hw.sensors.acpibat0.raw0=1 (battery discharging), OK
hw.sensors.acpibat0.raw1=1957 (rate)

Configure /etc/sensorsd.conf similar to:

Code: Select all

# alert if remaining capacity < warning capacity
hw.sensors.acpibat0.watthour3:low=0.43Wh:command=/usr/X11R6/bin/xmessage "battery is low"

Start/restart sensorsd via sudo /usr/sbin/sensorsd or sudo pkill -HUP sensorsd

Code: Select all

Set sensorsd_flags="" in /etc/rc.conf.local to stick around on boot.

If remaining capacity goes below the warning capacity, a xmessage pop-up will interrupt you.