Age | Commit message (Collapse) | Author | |
---|---|---|---|
2014-03-09 | Ignored Sandbox | Reto Hablützel | |
2014-03-07 | src/Plugins/Monitors/Volume.hs: port to alsa-mixer-0.2 | Sergei Trofimovich | |
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> | |||
2014-02-27 | NEWS update | Jose Antonio Ortega Ruiz | |
2014-02-25 | have disabled plugins still accept input | Adam Vogt | |
This change lets xmobar compiled without -fwith_inotify accept a config that mentions the Mail plugin with a warning (and display an Updating...). | |||
2014-02-23 | Credits for Marcin Mikołajczyk | Jose Antonio Ortega Ruiz | |
2014-02-21 | Update readme | Marcin Mikołajczyk | |
2014-02-20 | Change actions syntax | Marcin Mikołajczyk | |
2014-02-18 | Add support for multiple actions per item, activated depending on mouse ↵ | Marcin Mikołajczyk | |
button clicked | |||
2014-02-15 | Doc fixes | Jose Antonio Ortega Ruiz | |
2014-02-15 | Fix runaway memory leak when expanding invalid tags, and remove error | nand | |
Don't recursively parse on the case of an error. Also, in the case of an error, instead of replacing by an error message, replace by the tag itself to prevent mangling strings that legitimately include < and > characters, for example song titles when using the MPD plugin. I'm not sure how to handle this better. Honestly, I would like to remove the recursive parsing altogether but this works for now. Consider filing an issue for a proper resolution of this. I don't want rogue tags expanding themselves in my song titles. | |||
2014-02-06 | Doc update | Jose Antonio Ortega Ruiz | |
2014-02-06 | News update | Jose Antonio Ortega Ruiz | |
2014-02-05 | Handle errors better in Weather plugin | Ben Boeckel | |
2014-02-05 | Drop curl dependency for the HTTP module | Ben Boeckel | |
2014-02-05 | Find out whether the weather monitor is likely to block | Ben Boeckel | |
Uses the HTTP module to do the work rather than curl. | |||
2014-02-05 | Add a "ready" check to MPD monitors | Ben Boeckel | |
If the MPD server isn't responsive or the network is down, MPD will no longer block xmobar from doing its job. | |||
2014-02-05 | Add support for monitors to indicate they may block | Ben Boeckel | |
Useful when the network is down or something else is causing issues. | |||
2014-02-04 | Use MemAvailable from meminfo if possible | Ben Boeckel | |
Use the functionality from newer kernels if available. Basically, the free+buffer+cache metric is a massive hack and not accurate anyways (e.g., not all cache can be swapped out and kernel accounting can change whenever). Kernels 3.14 and newer have MemAvailable in meminfo which is more accurate; use it if possible. | |||
2014-02-05 | Couple of nits | Jose Antonio Ortega Ruiz | |
2014-02-05 | Fix for infinite loops when MPD is not running | Jose Antonio Ortega Ruiz | |
Should address #76 and #111. | |||
2014-02-05 | Version bump | Jose Antonio Ortega Ruiz | |
2014-02-05 | News | Jose Antonio Ortega Ruiz | |
2014-02-04 | Parse out fields from /proc/meminfo | Ben Boeckel | |
Newer kernels have changed the order of the lines in the /proc/meminfo find (MemAvailable is now line 3). To support this and older kernels, use the key from the map when getting data from it rather than static line numbers. | |||
2013-12-30 | Fix for time estimation when using the previous workaround | Jose Antonio Ortega Ruiz | |
2013-12-30 | Battery: workaround for obsolete current_now | Jose Antonio Ortega Ruiz | |
2013-12-30 | Fix for Top parsing of command lines containing blanks | Jose Antonio Ortega Ruiz | |
2013-11-25 | Merge dmalikov's feature/set-position | Jose Antonio Ortega Ruiz | |
2013-11-25 | findFiles renamed for directory-1.2.0.2 compat (fixes #137) | Jose Antonio Ortega Ruiz | |
2013-11-24 | Fix few typos | Pavlo Kapyshin | |
2013-11-24 | Get widest Rectangle instead of first one in setPosition | Dmitry Malikov | |
2013-10-29 | Fixed #133: xmobar was not reading ~/.xmobarrc | Thiago Negri | |
2013-10-29 | Fix xdgconf logic in readDefaultConfig | James McCoy | |
readDefaultConfig should prefer $XDG_CONFIG_HOME/xmobarrc if it exists, however the code was always reading path. This fixes the logic to actually use xdgconf if it exists. | |||
2013-10-27 | Doc formatting0.19 | Jose Antonio Ortega Ruiz | |
2013-10-27 | News update | Jose Antonio Ortega Ruiz | |
2013-10-27 | New N/A string monitor option (cf. #119) | Jose Antonio Ortega Ruiz | |
2013-10-27 | Some clarifications on Run (fixes #127) | Jose Antonio Ortega Ruiz | |
2013-10-27 | Using width options in wattage display (fixes #118) | Jose Antonio Ortega Ruiz | |
2013-09-13 | Tag 'action' of readme was not showing on GitHub page | Thiago Negri | |
2013-09-12 | Credits for Thiago Negri | Jose Antonio Ortega Ruiz | |
2013-09-11 | Created UnsafeStdinReader plugin | Thiago Negri | |
2013-08-29 | Fix for decoding problem in datetime plugin | Jose Antonio Ortega Ruiz | |
Should address issue #106 | |||
2013-08-14 | Typo fix: Wirelss instead of Wireless | Jacques-Pascal Deplaix | |
2013-08-13 | Version bump | Jose Antonio Ortega Ruiz | |
2013-08-11 | Bug tracker deprecation notice | Jose Antonio Ortega Ruiz | |
2013-08-11 | News and readme updates | Jose Antonio Ortega Ruiz | |
2013-08-11 | Merge branch 'safe-run-com' of https://github.com/00Davo/xmobar | Jose Antonio Ortega Ruiz | |
2013-08-11 | Plugins.Monitors.Weather: fix parsing of unknown station name | Sergei Trofimovich | |
reported by thunderrd Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> | |||
2013-08-11 | Run Coms using runInteractiveProcess, not runInteractiveCommand | David McLean | |
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 | |||
2013-07-20 | Honouring -d in CoreTemp | Jose Antonio Ortega Ruiz | |
Fixes issue #115 | |||
2013-07-12 | Back to regex-compat with a simpler POSIX regexp | Jose Antonio Ortega Ruiz | |