summaryrefslogtreecommitdiffhomepage
path: root/xmobar.cabal
AgeCommit message (Collapse)Author
2022-09-11cairo: alpha (still pseudo, via xrender)jao
2022-09-10cairo: fonts, offsets, colors, actionsjao
2022-09-09cairo: drawing skeleton from an xlib cairo surfacejao
2022-08-10changelog and version bump0.44.2jao
2022-08-09examples -> etcjao
2022-08-09whitespace: deps sorted in xmobar.cabaljao
2022-07-12Prepare dummy 0.44.1 release to mark transition to codebergjao
2022-07-12jao/xmobar -> xmobar/xmobarjao
2022-07-10Links to new repo in codebergjao
2022-05-12Remove the now useless -DUTF8 flagjao
2022-05-12Remove with_utf8 option and enable its features by default.Gleb Popov
2022-04-11add load monitor for freebsdMichal Zielonka
2022-03-30Changelog and version bumpjao
2022-03-30Load: new load average monitorjao
Closes #208
2022-03-27base < 4.17 to allow ghc 9.2.2jao
Fixes #617
2022-02-08Lower aeson version limitjao
2022-02-08Documentation bits and version bumpjao
2022-02-06swaybar-protocol: support for clickable Actionjao
2022-02-06swaybar-protocol: output with colors and actionsjao
2022-02-06swaybar-protocol: very basic formatjao
2022-02-04Refactoring: Xmobar.Text.{Ansi,Pango,Output}jao
2022-02-04Xmobar.App.TextEventLoop -> Xmobar.Text.Loopjao
2022-02-04Xmobar.App.X11EventLoop -> Xmobar.X11.Loopjao
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-29App.EventLoop -> App.X11EventLoopjao
2022-01-29Basic Xmobar.App.TextEventLoopjao
2022-01-29Xmobar.App.CommandThreadsjao
2022-01-29Xmobar.Run.Command -> Xmobar.Plugins.Commandjao
2022-01-16References to xmobar.org updated (fixes #599)jao
2021-12-17changelog/versionjao
2021-12-17add disk monitor for freebsdMichal Zielonka
2021-10-17start using kvm library from bsd for receiving swapinfoMichal Zielonka
Using this library allows us to receive swap info which is more similar with result of command swapinfo.
2021-10-16add top for freebsd procMichal Zielonka
In FreeBSD /proc/pid/stat is missing we should use for top procstat library.
2021-10-08try to add build action for freebsd + uptime plugin splitMichal Zielonka
2021-10-08try to reorganize modules per osMichal Zielonka
We should make better split os specify code for FreeBSD and Linux. Idea comes from @liskin.
2021-09-15Changelog and whitespacejao
2021-09-14Add the QueueReader plugin.Guy Gastineau
* A queue reader for xmobar using `TQueue a` from `stm`. This is a flexible and performat solution for sharing data between arbitrary haskell and xmobar. * I am not sure if I did the haddocks correctly.
2021-07-14Relax base requirements to allow build with GHC 9.0 (#557)Vladimír Štill
2021-07-13Add Kraken pluginAmir Saeid
2021-05-21changelog and authorsjao
2021-05-19Add k10temp pluginSam Kirby
The existing support for the coretemp kernel driver only works with Intel CPUs. This commit extends support for temperature monitoring to AMD CPUs. k10temp is a kernel driver for monitoring the temperature of AMD processors. It supports everything from AMD's 10h (Opteron/Athlon) family of processors to the latest 19h (Zen 3) family. Reference: https://www.kernel.org/doc/html/latest/hwmon/k10temp.html The meaning of the various temperatures made available has changed over the years and only `Tctl` is available on processors prior to the 17h family. Labels for these temperatures are present but as Tctl and Tdie do not contain a number I could not find a way to use these as `checkedDataRetrieval` expects an integer label. It is a PCI device and so an address needs to be supplied as part of the configuration. Example configuration: `Run K10Temp "0000:00:18.3" ["--template", "T: <Tdie>C | <Tccd1>C"] 60`
2021-05-19Version 0.380.38jao
2021-01-18Expose Xmobar.Plugins.Monitors.Common (fixes #520)jao
Exposing Common.Types and Common.Run is now redundant, but we could break configurations out there, so i'm not sure if we should remove them.
2020-12-20Including new .org doc files in extra-source-filesjao
2020-11-29Add new plugin: NotmuchMailslotThe
This plugin checks for new mail, provided that this mail is indexed by notmuch. As mail that was tagged is moved from the new directory to cur, the 'Mail' plugin (and its variants) won't work for such mail.
2020-11-19test: Fix flaky CpuSpecTomas Janousek
Failed at least once in GitHub Actions: predicate failed on: "Cpu: <fc=red>100</fc>% <fc=red>##########</fc>" Also, there's no need to guard the Xmobar.Plugins.Monitors.CpuSpec module with the with_alsa flag. (And it doesn't really work anyway, hspec-discover doesn't care about what modules are declared in cabal, so stack/ghc complains that "These modules are needed for compilation but not listed in your .cabal file's other-modules: Xmobar.Plugins.Monitors.AlsaSpec" and then fails to detect changes in those modules.)
2020-11-13Optimize Date plugin again (refresh timezone only once a minute)Tomas Janousek
This makes the Date plugin approximately twice as fast, and makes xmobar up to about 5–10 % faster if Date is the only active plugin. (If more expensive plugins like Network or MultiCpu are used, it doesn't make any measurable difference.) Micro-benchmark results on my HW: Date Benchmarks/Date mean 2.833 μs ( +- 16.08 ns ) Date Benchmarks/DateZonedTime mean 5.020 μs ( +- 32.91 ns ) Date Benchmarks/DateWithTimeZone mean 2.827 μs ( +- 20.52 ns ) (DateZonedTime is the original implementation and DateWithTimeZone is the implementation we had since 0.34 which never refreshes timezone.) Real-life measurements (done overnight on an idle laptop, with all measured xmobars running in parallel to ensure comparable conditions; xmobars configured to only display date and with rate 10 — once per second): $ time timeout 6h xmobar .xmobarrc-DateZonedTime real 360m0,010s user 0m9,867s sys 0m4,644s (9.867 + 4.644) / (360 * 60) = 0.000672 $ time timeout 6h xmobar .xmobarrc-Date real 360m0,008s user 0m9,535s sys 0m4,327s (9.535 + 4.327) / (360 * 60) = 0.000642 $ time timeout 6h xmobar .xmobarrc-Date-10m real 360m0,010s user 0m9,780s sys 0m4,215s (9.780 + 4.215) / (360 * 60) = 0.000648 $ time timeout 6h xmobar .xmobarrc-DateWithTimeZone real 360m0,006s user 0m9,658s sys 0m4,166s (9.658 + 4.166) / (360 * 60) = 0.000640 (.xmobarrc-Date-10m is the proposed implementation, but with timezone refresh every 10 minutes instead of every 1 minute) Interpretation of these results: * refreshing xmobar with just date takes around 650 μs * that is xmobar with just date uses around 0.065 % of CPU time * refreshing timezone takes additional cca 30 μs When we only refresh timezone once a minute, these 30 μs become 0.5 μs amortized, and that should be acceptable to even the most dedicated perfectionist :-) Fixes: a58e32f7c8af ("Revert "Optimize date plugin"") Fixes: 878db3908060 ("Optimize date plugin") Co-authored-by: Sibi Prabakaran <sibi@psibi.in>