summaryrefslogtreecommitdiffhomepage
path: root/doc
AgeCommit message (Collapse)Author
2024-03-17Make the Kbd monitor clickable, with click selecting the next layoutEnrico Maria De Angelis
2024-02-01documentation for with_shared and changelogjao
2024-01-19using-haskell.org: broken linksjao
2024-01-19quick-start.org: broken linksjao
2024-01-19plugins.org: broken linksjao
2024-01-19plugins.org: broken linksjao
2023-06-02center middle section for templates of the form "}M{" (fixes #677)jao
2023-03-26docs: comment on use of X11 fonts (fixes #658)jao
2023-01-05base 4.17 (ghc 9.4.x) and version bumpjao
2023-01-04relative link fixesjao
2023-01-04docs: bar sections and new alignment behaviourjao
2022-11-30Adds DPI configuration (#660)jgrocho
Adds a new DPI configuration, especially useful for HiDPI displays. This changes the scaling factor for fonts as displayed by Pango. It defaults to 96.0 which corresponds to an average screen and is the default in [Cairo](https://hackage.haskell.org/package/pango-0.13.5.0/docs/Graphics-Rendering-Pango-Cairo.html#v:cairoFontMapGetDefault). It's also possible to supply a zero or negative value to use the default scaling factor, but I felt setting the default to 96.0 makes it more explicit. It also adds a matching command line option. I haven't tested it too thoroughly, but in my limited use it appears to be working as intended. One thing this does not do is scale XBM and XPM bitmap files which I'm unsure how to do or if that should even be our concern (instead leaving it up to the user to supply appropriate bitmaps). Co-authored-by: Jonathan Grochowski <jon@grocho.net> Reviewed-on: https://codeberg.org/xmobar/xmobar/pulls/660 Co-authored-by: jgrocho <codeberg@jon.grocho.net> Co-committed-by: jgrocho <codeberg@jon.grocho.net>
2022-11-16docs: warning for 10-bit colour and Xrender (issue #651)jao
2022-11-08documentation and creditsjao
2022-10-17documentation nitjao
2022-10-17documentation nitjao
2022-09-28fix typosexorcist365
2022-09-28fixes to the above (or is it below?)jao
2022-09-28documentation updatesjao
2022-09-17docs: compilation instructions clean upsjao
2022-09-15new flag: with_xrenderjao
2022-09-15cairo: flags: with_xft gone and with_cairo true by defaultjao
2022-09-15cairo: box drawingjao
2022-09-12cairo: with_xft deprecated, with_cairo synomymjao
2022-08-13xmobar.el nitsjao
2022-08-09examples -> etcjao
2022-08-09xmobar.eljao
2022-07-24documentation: typosjao
2022-07-24documentation: text mode moved to quick start guidejao
2022-07-24documentation: interfacing-with-window-managers.org gonejao
2022-07-24documentation: all plugins in one basketjao
2022-07-24documentation tweaks (obsolete X tutorial link removed)jao
2022-07-24documentation nitsjao
2022-07-24documentation: header levels re-adjustedjao
2022-07-24documentation: improvements for xmobar-in-haskell docsjao
2022-07-24documentation: mini-tutorial on writting your own xmobar.hsjao
2022-07-16named anchors for sections mentioned in xmonad's docjao
2022-07-12jao/xmobar -> xmobar/xmobarjao
2022-07-10Links to new repo in codebergjao
2022-05-16Ditto for DynNetworkjao
2022-05-16Fix unit typosNils Trubkin
DynNetwork plugin might suffer from the same typo situation but I haven't confirmed it.
2022-04-18CpuFreq: new template parameters max, min and avg.jao
Fixes #166.
2022-04-18New dbus signal: SetAlpha (fixes #499)jao
2022-04-14Memory: new argument to scale usage unitsjao
Fixes #624
2022-03-30Load: honour the -d (decimal digits) monitor argumentjao
2022-03-30Load monitor: correctly colorize according to -L/-Hjao
2022-03-30Load: new load average monitorjao
Closes #208
2022-02-20Documentation: Note the need for threaded RTS with QueueReader & xmonadTomas Janousek
Related: https://github.com/jaor/xmobar/issues/571
2022-02-20Documentation: More robust QueueReader exampleTomas Janousek
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
2022-02-20Documentation: Drop unused fragment in QueueReader exampleTomas Janousek
Related: https://github.com/jaor/xmobar/issues/571