No description
57f69e900b
Even if we extend the flag to be an n-flag with a numerical input, we
already have other Unix-tools to take care of us much more flexibly,
e.g. with head(1) you can easily get the first 10 outputs with
slstatus -s | head -n 10,
but also e.g. discard the first one and then get the consecutive 10
outputs.
For the X11-root-window-name, you can limit the runtime with timeout(1)
or a comparable solution.
This reverts commit
|
||
---|---|---|
components | ||
arg.h | ||
config.def.h | ||
config.mk | ||
LICENSE | ||
Makefile | ||
README | ||
slstatus.1 | ||
slstatus.c | ||
slstatus.h | ||
util.c | ||
util.h |
slstatus - suckless status ========================== slstatus is a suckless status monitor for window managers that use WM_NAME (e.g. dwm) or stdin to fill the status bar. Features -------- - Backlight percentage - Battery percentage/state/time left - CPU usage - CPU frequency - Custom shell commands - Date and time - Disk status (free storage, percentage, total storage and used storage) - Available entropy - Username/GID/UID - Hostname - IP address (IPv4 and IPv6) - Kernel version - Keyboard indicators - Load average - Network speeds (RX and TX) - Number of files in a directory (hint: Maildir) - Memory status (free memory, percentage, total memory and used memory) - Swap status (free swap, percentage, total swap and used swap) - Temperature - Uptime - Volume percentage (OSS/ALSA) - WiFi signal percentage and ESSID Requirements ------------ In order to build slstatus you need the Xlib header files. Installation ------------ Edit config.mk to match your local setup (slstatus is installed into the /usr/local namespace by default). Uncomment OSSLIBS on OpenBSD. Afterwards enter the following command to build and install slstatus (if necessary as root): make clean install Running slstatus ---------------- See the man page for details. Configuration ------------- slstatus can be customized by creating a custom config.h and (re)compiling the source code. This keeps it fast, secure and simple. Todo ---- Cleaning up the whole codebase it the goal before thinking about a release.