1

Related: Why are my monospace fonts behaving erratically?

No matter what input I give fc-match, it always returns the same thing. I think this is the root cause of the related Q above.

output

How would I go about debugging this issue?


Following-up on the comment section, the output of FC_DEBUG=4 fc-match mono is available in this pastebin. Far more output than SE allows.

8
  • Your font-config configuration files are messed up. Try completely removing and reinstalling it.
    – Larssend
    Jul 25, 2015 at 3:41
  • @Larssend Hmm, any idea on how to completely remove it? pacman won't let me uninstall it since it's required by other packages (and there doesn't seem to be an option to force the matter). I tried forcing an install (which conveniently updated the font cache), but I don't think it removed any of the existing files. Jul 25, 2015 at 3:47
  • I did find englanders.us/~jason/howtos.php?howto=fontconfig (scroll to the bottom) and am going to be trying the 'hands-on' approach, as it were. Unless there's a better option, of course :) Jul 25, 2015 at 3:49
  • @Larssend No luck with the manual remove / reinstall approach :( Jul 25, 2015 at 3:55
  • Re-installed all packages with pacman -Qns | pacman -S - and rebooted – still no luck. Jul 25, 2015 at 4:36

1 Answer 1

0

This isn't a solution so much as a hack-around.

From How to set default fonts and font aliases on Linux, I added the following within the <fontconfig> node of ~/config/fontconfig/fonts.conf:

<alias>
  <family>monospace</family>
  <prefer><family>Source Code Pro</family></prefer>
  <!-- Obviously, customize your preference above -->
</alias>

I'm still very much interested in a real solution for this.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .