denbeigh2000 / goi3bar Goto Github PK

the underlying call to ip still fails when we query for the network device - verification should probably be done using procfs somehow so failures are more graceful and deterministic.

We can improve on this by using json.RawMessage in place of interface{}, so that processing is deferred instead of re-performed.

I'm not sure why, but on my system, iwconfig never shows the signal strength. So, I always get the following error: Error generating output for network: Couldn't match strength

wlp5s0    IEEE 802.11abg  ESSID:"lalala"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: 30:B5:C2:08:5A:D9   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off

I think in this case goi3bar can just skip the signal strength.
That's on my laptop with wl driver for Broadcom wi-fi chip.

We have system load, but I would like cpu % (total) as well

I had to navigate to the cmd/goi3bar directory and run go install there to get it to build.

Using go 1.7.3 on ubuntu 16.04

Use https://golang.org/pkg/text/template/?

bar { entry in my ~/.i3/config looks like:

bar {
    status_command goi3bar -config-path ~/.i3/goi3status.json
}

And the config file was taken from the README.md on the repo:

{
    "colors": {
        "color_crit": "#FF0000",
        "color_warn": "#FFA500",
        "color_ok": "#00FF00",
        "color_general": "#FFFFFF"
    },
    "interval": "5s",
    "entries": [
        {
            "package": "memory",
            "name": "memory",
            "options": {
                "interval": "10s",
                "warn_threshold": 75,
                "crit_threshold": 85
            }
        }
    ]
}

Running the goi3bar command as mentioned in i3config file works without any errors and I see output beng emitted onto stdout every few seconds. However, it doesn't run through i3wm and throws error as mentioned in the subject.

• Show ip address
• Show connected wifi network (if available)
• Show connected speed
• Show current downstream rate
• Show current upstream rate

Hi!

As you have stated in the readme it doesn't support all types of laptop batteries. To support for Dell XPS 13, and other laptops from Dell I suppose, you would need these changes.

RasmusLindroth@a534134

I could help you implement it but I'm not sure what the best way is. One alternative would be to would have to state your model in the configuration file, but I think the more cleaner solution would be to check if either POWER_SUPPLY_ENERGY_FULL or POWER_SUPPLY_CHARGE_FULL is set in /sys/class/power_supply/BAT0/subsystem/...

By the way, thank you for your software :)

I don't want to write golang to customise my bar. I would rather have some sort of config file