Closed iliayar closed 2 years ago
@iliayar we now have the CI set up for the X11-xft repo, so could you PR that portion of this against https://github.com/xmonad/X11-xft? Thanks!
Posting this conversation from IRC so it's not lost:
<liskin> Solid: have you thought the X11-xft dependency bump through? (I
haven't, but someone should)
<liskin> Solid: stack init with only xmonad/xmonad-contrib might break,
perhaps? or will it automatically detect that X11-xft needs to
be added to extra-deps?
<Solid> liskin: stack is smart, but not in a way that's benneficial to
us :/ It doesn't seem to care about the projects stack.yaml
file, only about the cabal file.
<Solid> If xft specifies a version bound that stack can't find in a
snapshot it'll just disable the flag
<Solid> but otherwise it tries to download the newest x11-xft on
stackage and doesn't include contrib's extra deps
<liskin> Solid: in that case we might need to ifdef the new
functionality :-/
Thanks!
Description
Related to #208. Moving MinXft library and xmobar's fallback fonts logic to XMonad prompts, tabs labels, etc. So now, for example, prompts are able to display text and emoji. You can specify fonts to use through comma-separated list. It also requires manual bindings from the Xft library, because https://hackage.haskell.org/package/X11-xft doesn't have binding for vital
XftCharExists
function.Checklist
[X] I've read CONTRIBUTING.md
[ ] I've considered how to best test these changes (property, unit, manually, ...) and concluded: XXX
[ ] I updated the
CHANGES.md
file