Noto Mono Font Issue

[mmcdole]

In the font config file we have:

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
    <match>
        <edit mode="prepend" name="family"><string>Noto Sans</string></edit>
    </match>
    <match target="pattern">
        <test qual="any" name="family"><string>serif</string></test>
        <edit name="family" mode="assign" binding="same"><string>Noto Serif</string></edit>
    </match>
    <match target="pattern">
        <test qual="any" name="family"><string>sans-serif</string></test>
        <edit name="family" mode="assign" binding="same"><string>Noto Sans</string></edit>
    </match>
    <match target="pattern">
        <test qual="any" name="family"><string>monospace</string></test>
        <edit name="family" mode="assign" binding="same"><string>Noto Mono</string></edit>
    </match>
</fontconfig>

I believe Noto Mono has been renamed Noto Sans Mono. I noticed that monospace fonts weren't working in Chrome. The command fc-match monospace was also not returning Noto Mono but was returning Noto Sans. I then switched the above to Noto Sans Mono, refreshed the font-cache and re-launched chrome and they were working.

Confirm this if you can. http://patorjk.com/software/taag/#p=display&f=Graffiti&t=Type%20Something%20 to see a site that has monospace fonts.

[ejmg]

Hey @mmcdole so sorry it took me this long to respond.

Here is what my font config shows:

.

I am wondering where/when I chose to set Hack as my monospace(?) font, but then when I then run fc-match monospace, I get DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book", so now I am doubly confused.

As it stands, I am fairly sure I am getting monospace fonts rendered on my system despite of what I have put in the guide. That said, would simply changing the config to Noto Sans Mono affect the change we need to fix this?

[ejmg]

I have been building a small list of weird quirks I have discovered on my system in the issues in case you have not seen them recently, btw. Let me know if any of them effect you, particularly #17!