summaryrefslogtreecommitdiffhomepage
path: root/src/Xmobar/Run
AgeCommit message (Collapse)Author
2022-09-11x event loop clean-upsjao
2022-09-11cairo: outer borderjao
2022-02-07swaybar-protocol: additionalFonts via pango markupjao
2022-02-06swaybar-protocol: support for clickable Actionjao
2022-02-04Refactoring: event loop handling simplificationsjao
2022-02-04Xmobar.X11.Parsers -> Xmobar.Run.Parsersjao
2022-02-04Xmobar.App.CommandThreads -> Xmobar.Run.Loopjao
2022-02-04Xmobar.App.Timer -> Xmobar.Run.Timerjao
2022-02-03Xmobar.X11.Actions -> Xmobar.Run.Actionsjao
2022-01-29Xmobar.Run.Command -> Xmobar.Plugins.Commandjao
2021-07-13Add Kraken pluginAmir Saeid
2021-05-24Merge branch 'notmuchmail-fix' [#548]jao
2021-05-24Add NotmuchMail as a runnable typeslotThe
This is needed for the plugin to parse properly in non-Haskell based configurations. Related: https://github.com/jaor/xmobar/issues/547
2021-05-22Add show instances for several types so that configs can be generated ↵Ryan Trinkle
programmatically
2020-05-02Update stderr and the bar on receiving exceptionSibi Prabakaran
2020-04-30Refactor the usage of hGetLineSafeSibi Prabakaran
hGetLineSafe is always hGetLine and hence we can directly use it.
2020-02-22Timer coalescing: gracefully uncoalesce slow timersTomas Janousek
The first implementation assumed all timers (monitors) are fast and frequent (which happens to be the case in my configuration). This meant that a single on-line weather monitor could block the entire xmobar instance for a long time due to the refresh pausing (meant to reduce power consumption). This commit attempts to fix that by limiting the refresh pause time and using the old periodic sleep method for these slow timers (monitors).
2020-02-22Implement 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-22Refactor code from tenthSeconds to doEveryTenthSecondsTomas Janousek
A preparation for timer coalescing: tenthSeconds is just a sleep whereas doEveryTenthSeconds enables using a central timer and waiting for all monitors to update before refreshing the window. This commit is just a simple refactor, the actual timer coalescing code comes later.
2018-12-02Fix: exposing the Command constructors in libjao
2018-11-26Xmobar.Config.Parsejao
2018-11-25Xmobar.System.Utils, Xmobar.X11.Eventsjao
2018-11-25Xmobar.App.Mainjao
2018-11-25Xmobar.App and small refactoringsjao
2018-11-25Back to app/src, since it seems they're the default convention for stackjao