summaryrefslogtreecommitdiffhomepage
AgeCommit message (Collapse)Author
2014-03-09Ignored SandboxReto Hablützel
2014-03-07src/Plugins/Monitors/Volume.hs: port to alsa-mixer-0.2Sergei Trofimovich
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
2014-02-27NEWS updateJose Antonio Ortega Ruiz
2014-02-25have disabled plugins still accept inputAdam 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-23Credits for Marcin MikołajczykJose Antonio Ortega Ruiz
2014-02-21Update readmeMarcin Mikołajczyk
2014-02-20Change actions syntaxMarcin Mikołajczyk
2014-02-18Add support for multiple actions per item, activated depending on mouse ↵Marcin Mikołajczyk
button clicked
2014-02-15Doc fixesJose Antonio Ortega Ruiz
2014-02-15Fix runaway memory leak when expanding invalid tags, and remove errornand
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-06Doc updateJose Antonio Ortega Ruiz
2014-02-06News updateJose Antonio Ortega Ruiz
2014-02-05Handle errors better in Weather pluginBen Boeckel
2014-02-05Drop curl dependency for the HTTP moduleBen Boeckel
2014-02-05Find out whether the weather monitor is likely to blockBen Boeckel
Uses the HTTP module to do the work rather than curl.
2014-02-05Add a "ready" check to MPD monitorsBen 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-05Add support for monitors to indicate they may blockBen Boeckel
Useful when the network is down or something else is causing issues.
2014-02-04Use MemAvailable from meminfo if possibleBen 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-05Couple of nitsJose Antonio Ortega Ruiz
2014-02-05Fix for infinite loops when MPD is not runningJose Antonio Ortega Ruiz
Should address #76 and #111.
2014-02-05Version bumpJose Antonio Ortega Ruiz
2014-02-05NewsJose Antonio Ortega Ruiz
2014-02-04Parse out fields from /proc/meminfoBen 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-30Fix for time estimation when using the previous workaroundJose Antonio Ortega Ruiz
2013-12-30Battery: workaround for obsolete current_nowJose Antonio Ortega Ruiz
2013-12-30Fix for Top parsing of command lines containing blanksJose Antonio Ortega Ruiz
2013-11-25Merge dmalikov's feature/set-positionJose Antonio Ortega Ruiz
2013-11-25findFiles renamed for directory-1.2.0.2 compat (fixes #137)Jose Antonio Ortega Ruiz
2013-11-24Fix few typosPavlo Kapyshin
2013-11-24Get widest Rectangle instead of first one in setPositionDmitry Malikov
2013-10-29Fixed #133: xmobar was not reading ~/.xmobarrcThiago Negri
2013-10-29Fix xdgconf logic in readDefaultConfigJames 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-27Doc formatting0.19Jose Antonio Ortega Ruiz
2013-10-27News updateJose Antonio Ortega Ruiz
2013-10-27New N/A string monitor option (cf. #119)Jose Antonio Ortega Ruiz
2013-10-27Some clarifications on Run (fixes #127)Jose Antonio Ortega Ruiz
2013-10-27Using width options in wattage display (fixes #118)Jose Antonio Ortega Ruiz
2013-09-13Tag 'action' of readme was not showing on GitHub pageThiago Negri
2013-09-12Credits for Thiago NegriJose Antonio Ortega Ruiz
2013-09-11Created UnsafeStdinReader pluginThiago Negri
2013-08-29Fix for decoding problem in datetime pluginJose Antonio Ortega Ruiz
Should address issue #106
2013-08-14Typo fix: Wirelss instead of WirelessJacques-Pascal Deplaix
2013-08-13Version bumpJose Antonio Ortega Ruiz
2013-08-11Bug tracker deprecation noticeJose Antonio Ortega Ruiz
2013-08-11News and readme updatesJose Antonio Ortega Ruiz
2013-08-11Merge branch 'safe-run-com' of https://github.com/00Davo/xmobarJose Antonio Ortega Ruiz
2013-08-11Plugins.Monitors.Weather: fix parsing of unknown station nameSergei Trofimovich
reported by thunderrd Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
2013-08-11Run Coms using runInteractiveProcess, not runInteractiveCommandDavid 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-20Honouring -d in CoreTempJose Antonio Ortega Ruiz
Fixes issue #115
2013-07-12Back to regex-compat with a simpler POSIX regexpJose Antonio Ortega Ruiz
generated by cgit v1.2.3 (git 2.39.1) at 2024-10-30 09:27:48 +0000