xmobar/doc, branch 0.44 a minimalistic status bar https://jao.io/cgit/xmobar/atom?h=0.44 2022-05-16T01:49:10Z Ditto for DynNetwork 2022-05-16T01:49:10Z jao jao@gnu.org 2022-05-16T01:49:10Z urn:sha1:67eb936cea41cfa601053b613e42eb8bb63090f9 Fix unit typos 2022-05-16T01:12:36Z Nils Trubkin 32000568+nils-trubkin@users.noreply.github.com 2022-05-16T01:12:36Z urn:sha1:7e16892a40d432e3f195da7adc46750761facabc DynNetwork plugin might suffer from the same typo situation but I haven't confirmed it. CpuFreq: new template parameters max, min and avg. 2022-04-18T17:55:04Z jao jao@gnu.org 2022-04-18T17:55:04Z urn:sha1:552d6f8baa1048ddb5fd22269efd50b90303ca4d Fixes #166. New dbus signal: SetAlpha (fixes #499) 2022-04-18T14:59:51Z jao jao@gnu.org 2022-04-18T14:59:51Z urn:sha1:082ef98c1c265ad927b728402d8803a86bbbaeef Memory: new argument to scale usage units 2022-04-14T15:41:36Z jao jao@gnu.org 2022-04-14T15:41:36Z urn:sha1:727478f5b8916d8d98ae4208d4f6a80abb4fafc7 Fixes #624 Load: honour the -d (decimal digits) monitor argument 2022-03-30T18:22:13Z jao jao@gnu.org 2022-03-30T18:22:13Z urn:sha1:88230bb0301aebc37c971d235f5a9735d9563f8d Load monitor: correctly colorize according to -L/-H 2022-03-30T05:17:42Z jao jao@gnu.org 2022-03-30T05:17:42Z urn:sha1:60b106ac0db19800667ee54b0d390d80e0873b52 Load: new load average monitor 2022-03-30T01:37:00Z jao jao@gnu.org 2022-03-30T01:37:00Z urn:sha1:4f4e8de1d8b4d33e02057d085399d25e05d87a17 Closes #208 Documentation: Note the need for threaded RTS with QueueReader & xmonad 2022-02-20T19:57:31Z Tomas Janousek tomi@nomi.cz 2022-02-20T19:56:21Z urn:sha1:efa9e4c541695e725d39da001592c9613acc4cae Related: https://github.com/jaor/xmobar/issues/571 Documentation: More robust QueueReader example 2022-02-20T19:57:28Z Tomas Janousek tomi@nomi.cz 2022-02-20T19:52:54Z urn:sha1:7cca823651a4a33e0c99d4062a382704f7904572 1. Call `initThreads` early because there's no guarantee the xmobar thread will do this before xmonad makes any Xlib calls (although it's likely as xmonad startup is probably more expensive). 2. Use `forkOS` to fail early if running in a non-threaded RTS. Also, xmobar's own main thread would normally be a bound thread, so this may (likely non-observably) result in more consistent behaviour. Related: https://github.com/jaor/xmobar/issues/571