Usage
-----
+`make build && make install`
+
+`make install` copies everything from `./bin` to `$HOME/bin`
+
In my `~/.xinitrc` I have something like the following:
```sh
-v Opt_Mpd_Song_Max_Chars=10 \
-v Opt_Net_Interfaces_To_Show=wlp3s0 \
-v Opt_Pulseaudio_Sink=0 \
+ -f <(./bin/khatus_gen_make_status_bar \
+ -v Status_Bar='@energy,@memory,@processes,@cpu,@disk,@net,@bluetooth,@backlight,@volume,@mpd,@weather,@datetime' \
+ ) \
| "$BIN"/khatus_actuate_status_bar_to_xsetroot_name \
) \
>(stdbuf -o L "$BIN"/khatus_monitor_energy \
TODO
----
+- formalize message format and protocol
- tests (design is starting to take shape, so it is time)
- show how many Debian package updates are available
- show how many Debian package security-updates are available
Ideas
-----
-- make `khatus` a daemon, so we don't have to re-launch X to re-launch `khatus`
+- track devices:
+ - alert when never before seen device is plugged-in
+ - report history and trends on when and how-often each
+ device/category is plugged-in, how-long it stays plaugged-in, etc.
+- daemonize `khatus`, so we don't have to re-launch `X11` to re-launch `khatus`
+- interoperate with other khatus instances
+ - prefix machine ID to each data source
+ (What should that ID be? Hostname? Pub key?)
+ - fetch remote data and process locally
+ - what transport to use?
+ - ssh + rsync + cache dumps per some interval?
+ - `A` can setup self penetration testing, by setting up probe of `A` on `B`
+ and fetching results from `B` to `A`
- offline mode - quick disable all network-using subsystems (sensors, monitors, etc)
- classify each sensor as either "local" or "remote" (what about `iwconfig`, et al?)
- store data with rrdtool