xmobar/src, branch 0.19

New N/A string monitor option (cf. #119)

2013-10-27T15:20:25Z

Using width options in wattage display (fixes #118)

2013-10-27T14:24:37Z

Created UnsafeStdinReader plugin

2013-09-12T01:05:12Z

Fix for decoding problem in datetime plugin

2013-08-29T15:55:50Z

Should address issue #106

Version bump

2013-08-13T18:13:10Z

Merge branch 'safe-run-com' of https://github.com/00Davo/xmobar

2013-08-11T21:04:34Z

Plugins.Monitors.Weather: fix parsing of unknown station name

2013-08-11T16:18:44Z

reported by thunderrd Signed-off-by: Sergei Trofimovich

Run Coms using runInteractiveProcess, not runInteractiveCommand

2013-08-11T04:29:18Z

The API exposed by Com is command -> [arguments] -> alias -> timeout -> Com. Since the command and arguments are separated like this, one would assume that the command is run "safely": The arguments are already separated in the arg list, so the command should be run without passing through a shell, which ensures that stray shell metacharacters in the arguments don't mess up anything. However, previous versions simply joined the command with its arguments into one string and then passed that string into a shell to run. This is counter-intuitive given the seemingly "safe" API exposed by Com, so using runInteractiveProcess instead is the correct implementation. Note that users may still run commands that need shells by being explicit about it, like this: Run Com "/bin/bash" ["-c", "command | nextCommand & parallelCommand"] 60

Honouring -d in CoreTemp

2013-07-20T11:52:58Z

Fixes issue #115

Back to regex-compat with a simpler POSIX regexp

2013-07-12T20:11:03Z