Age | Commit message (Collapse) | Author | |
---|---|---|---|
2024-02-05 | actions: spawnCommand instead of deprecated system | jao | |
This should address the problems reported in issue #688 | |||
2022-09-30 | Run.Parsers -> Config.Template | jao | |
2022-09-16 | little clean-ups | jao | |
2022-09-15 | cairo: box drawing | jao | |
2022-09-14 | whitespace | jao | |
2022-09-11 | x event loop clean-ups | jao | |
2022-09-11 | cairo: outer border | jao | |
2022-02-07 | swaybar-protocol: additionalFonts via pango markup | jao | |
2022-02-06 | swaybar-protocol: support for clickable Action | jao | |
2022-02-04 | Refactoring: event loop handling simplifications | jao | |
2022-02-04 | Xmobar.X11.Parsers -> Xmobar.Run.Parsers | jao | |
2022-02-04 | Xmobar.App.CommandThreads -> Xmobar.Run.Loop | jao | |
2022-02-04 | Xmobar.App.Timer -> Xmobar.Run.Timer | jao | |
2022-02-03 | Xmobar.X11.Actions -> Xmobar.Run.Actions | jao | |
2022-01-29 | Xmobar.Run.Command -> Xmobar.Plugins.Command | jao | |
2021-07-13 | Add Kraken plugin | Amir Saeid | |
2021-05-24 | Merge branch 'notmuchmail-fix' [#548] | jao | |
2021-05-24 | Add NotmuchMail as a runnable type | slotThe | |
This is needed for the plugin to parse properly in non-Haskell based configurations. Related: https://github.com/jaor/xmobar/issues/547 | |||
2021-05-22 | Add show instances for several types so that configs can be generated ↵ | Ryan Trinkle | |
programmatically | |||
2020-05-02 | Update stderr and the bar on receiving exception | Sibi Prabakaran | |
2020-04-30 | Refactor the usage of hGetLineSafe | Sibi Prabakaran | |
hGetLineSafe is always hGetLine and hence we can directly use it. | |||
2020-02-22 | Timer coalescing: gracefully uncoalesce slow timers | Tomas 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-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 | Refactor code from tenthSeconds to doEveryTenthSeconds | Tomas 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-02 | Fix: exposing the Command constructors in lib | jao | |
2018-11-26 | Xmobar.Config.Parse | jao | |
2018-11-25 | Xmobar.System.Utils, Xmobar.X11.Events | jao | |
2018-11-25 | Xmobar.App.Main | jao | |
2018-11-25 | Xmobar.App and small refactorings | jao | |
2018-11-25 | Back to app/src, since it seems they're the default convention for stack | jao | |