Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-02-22 | Implement timer coalescing (noticeably less CPU/power usage) | Tomas Janousek | |
xmobar currently runs every monitor in its own thread. Monitors that do periodic updates simply sleep and loop. This unfortunately leads to these threads coming out of sync, and xmobar ends up waking up and redrawing for every periodic monitor. In my case, that is 7 times per second, which is enough for xmobar to be at the top of "top" with more than 1% CPU usage, and to have a noticeable impact on battery life. This commit adds a central timer coordination thread which makes sure that periodic updates happen together and that we only redraw once they're all done. Together with PR #409, I managed to lower the idle power draw of my laptop from 4W to 3W. | |||
2020-02-22 | Silence some warnings | Tomas Janousek | |
src/Xmobar/X11/Draw.hs:51:11-12: warning: [-Wunused-matches] Defined but not used: ‘wr’ | 51 | drawInWin wr@(Rectangle _ _ wid ht) ~[left,center,right] = do | ^^ src/Xmobar/App/EventLoop.hs:50:1-36: warning: [-Wunused-imports] The import of ‘Xmobar.X11.Events’ is redundant | 50 | import Xmobar.X11.Events(nextEvent') | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |||
2018-12-02 | Fix: exposing the Command constructors in lib | jao | |
2018-11-30 | Self-compilation a la xmonad | jao | |
2018-11-25 | Xmobar.System.Utils, Xmobar.X11.Events | jao | |
2018-11-25 | X11.XUtil -> X11.Text | jao | |
2018-11-25 | Xmobar.App.Defaults and Xmobar.Config.Types | jao | |
2018-11-25 | Xmobar.X11.Actions | jao | |
2018-11-25 | Xmobar.App and small refactorings | jao | |