xmobar/src/Plugins, branch 0.23

Added additional wind parser case for "Variable at"

2015-02-01T02:21:31Z

Wind data sometimes looks like this: "Wind: Variable at 3 MPH (3 KT):0" Note the missing direction info. This fix adds an additional parser for this case to pWind.

Honour the -S (show suffix) monitor flag in CpuFreq

2014-12-26T17:20:49Z

MPD: add a new template variable 'flags'

2014-12-15T04:29:58Z

Displays playback flags in the style of ncmpcpp.

Introduce available memory variables in memory monitor

2014-11-12T20:23:54Z

Available memory is determined from meminfo's `MemAvailable:` on 3.14 and newer, and falls back to `free + buffer + cache` on older systems. Introduces new variables ``.

Using fromMaybe

2014-09-27T22:36:33Z

Upgrade to libmpd 0.9

2014-09-27T22:25:54Z

Merge branch 'dynamic-strings' of https://github.com/projedi/xmobar

2014-09-24T18:54:16Z

Rename dynamic string to icon pattern

2014-09-24T08:31:54Z

Locks: Implement event-driven locks indicator

2014-09-17T03:20:11Z

This commit does more fundamental rework of the "Locks" plug-in: now the plug-in is fully event-driven and thus extremely power-efficient, effectively zero CPU consumption while idling.

Locks: Rework to avoid unnecessary display reopening

2014-09-17T03:20:10Z

The extremely useful "Locks" plugin eats quite a lot of CPU (>2% here on a old-ish laptop), unfortunately. The plug-in unnecessary reopens the display, which is quite expensive operation. It results into 16 syscalls: socket(PF_LOCAL) -> connect(sun_path=@"/tmp/.X11-unix/X0"}) -> getpeername() -> uname() -> access(".Xauthority") -> open(".Xauthority") -> fstat() -> mmap() -> read() -> close() -> munmap() -> getsockname() -> fcntl(F_SETFD) -> fcntl(F_SETFL) -> shutdown() -> close() This is almost half of all the syscalls that we ought to execute for the plug-in to work. Now, considering the useful work and that "Locks" runs every 200 milliseconds, it gives us >300 syscalls (and a lot more wake-ups) per second. This commit fixes the reopening issue, effectively halving the CPU consumption (down to ~1%). The patch also makes it easier to implement event-driven indicators that will reduce the idle CPU consumption to 0.