summaryrefslogtreecommitdiffhomepage
AgeCommit message (Collapse)Author
2024-03-06readme: more broken linksjao
2024-03-06readme.org: absolute links (fixes #694)jao
2024-03-03changelogjao
2024-02-18battery: spawnCommand instead of system when running actions0.47.4jao
should fix for real #688 this time
2024-02-07version tag and changelog0.47.3jao
2024-02-05actions: spawnCommand instead of deprecated systemjao
This should address the problems reported in issue #688
2024-02-01readme.org: author listjao
2024-02-01documentation for with_shared and changelogjao
2024-01-31Bump base dependencyVekhir
Builds and tests fine
2024-01-31Add `with_shared` flag to build using shared librariesVekhir
Adds the `with_shared` flag, which is off by default. Setting the new flag enables building with shared libraries. By default, `xmobar` is built with static linking.
2024-01-31Enable use of shared librariesVekhir
Haskell libraries can be linked statically or dynamically. Either way, all packages must be linked the same way. This means that if all dependencies of `xmobar` are shared libraries, then `xmobar` itself must be built using dynamic linking. Therefore, to compile the individual `xmobar` executables, add the `-dynamic` flag to signal that they are built with shared libraries. This flag is put behind an #ifdef to easily configure static vs dynamic linking. To use shared libraries, define SHARED_LIBRARIES
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
2024-01-19readme.org: broken linksjao
2024-01-19readme.org: broken linksjao
2023-11-12fix: dependendecy on mtl to allow GHC 9.60.47.2jao
2023-11-12fix: dependendecy on base to allow GHC 9.6jao
2023-11-11compatibility with GHC 9.6jao
2023-09-02typojao
2023-09-02docs and changelog on libmpd0.47.1jao
2023-09-01allow requesting explicitly libmpd with with_mpd for any ghc versionjao
2023-08-30woodpecker: pipeline -> stepsjao
2023-08-30changelog and copyright years0.47jao
2023-08-30version bumpjao
2023-08-30.drone.yml -> .woodpecker.ymljao
2023-08-28exclude libmpd for ghc 9.4 or greaterjao
2023-07-11Add FreeBSD installation instructionJaroslaw Jantura
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-03-22Handle SocketError when attempting to connect to dbusCorey Halpin
Extends the solution from 8a53271cd6 to also handle SocketError, so that the process will not terminate. See also issue #537.
2023-01-17stack dependencies for cairo/pango (fixes #666)jao
2023-01-05typojao
2023-01-05testing with ghc 9.2 for now (again)0.46jao
2023-01-05testing with ghc 9.2 for now (again)jao
2023-01-05testing with ghc 9.2.5 for nowjao
2023-01-05testing with ghc 9.2 for nowjao
pango seems to be incompatible with ghc 9.4.4 because it needs text < 2.
2023-01-05trying to fix deps for ghc 9.4.4jao
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-12-31layout: special case for empty left segment (see #655)jao
2022-12-23Fix for #663: honour explicit bg/fg colors for iconsjao
2022-12-10off by onesjao
2022-12-10off by onejao
2022-12-10alignment: avoid overlapping of left and right segmentsjao
Might help with #655
2022-11-30lintingjao
2022-11-30changelog and author for previous commitjao
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>