DeeDeeG/fc-match -s "Segoe UI Emoji".bash

I got it in #2

.fonts.conf

<?xml version='1.0'?> 
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'> 
<fontconfig> 
  <match target="pattern"> 
    <edit name="family" mode="prepend"> 
      <string>Noto Color Emoji</string>
      <!--<string>Twitter Color Emoji</string>-->
    </edit> 
  </match> 
</fontconfig>

The only ideas I have to fix this come from reading https://github.com/eosrei/emojione-color-font and the fontconfig file he uses.

• You might be able to try "mode=prepend_first" rather than "mode=prepend".

• Or you might be able to prepend Bitsream Vera before Noto Color Emoji, because Bistream Vera has none of the black and white emojis... and it may ensure no black and white emojis show up, by bumping DejaVu Sans out of first place.

• You can add a number to the beginning of your .conf's filename, which gives the file a priority of some kind, relative to other .conf files on the system. (Is it 1 - 100? Is 1 highest proprity, or is 100 highest priority? I don't know the details. He uses 56, as in "56-[sometext].conf")

• Lastly, although I'm not sure if any of these suggestions work, two related suggestions: You could place the noto font in [your-home-dir]/.local/share/fonts/[noto-font-file-here]

• And you can place the fontconfig file in [your-home-dir]/.config/fontconfig/conf.d/[your-.conf-file-here]

(Last two suggestions are from his install script.)

If you end up using any of these suggestions maybe he should get credit in your license.md or readme.md, but I leave that to you to decide.

You might be able to try "mode=prepend_first" rather than "mode=prepend".

I would not advise prepend_first for an emoji font. It will mess up text if it is the primary font applied. You want a regular font to supply the usual normal text glyphs, and fallback to emoji. There are various ways to do this, and some have used prepend_first in combination with a regular font like Bitstream Vera so that two fonts are placed at the start of the font list being generated. So long as no other third-party config is trying the same approach, you shouldn't have to be concerned about any races for priority and this will probably work fine...but afaik it would likely also equate to enforcing that font over any other, which might not be desirable?(I have not confirmed if that happens but I think it does).

Is it 1 - 100? Is 1 highest proprity, or is 100 highest priority? I don't know the details.

They actually have designated purposes for the different stages of building a font list, as mentioned here. Unfortunately that's not always reliable when third-party fonts are involved with their own configs that treat it as priority alone(which technically works, but can result in confusion with interactions from other configs/rules timing).

00 is the lowest and will be run first, followed by 99 at the end as last. 50 should have a 50-user.conf file which will load user config, which can be a single config file or it's own conf.d(which afaik is more like a priority in the sense that I believe these all load from that halfway point, and when finished will resume the remainder of system configs from 50, I've not verified that). The one notable case where 50 is a bit too late, is due to 49-sansserif.conf which will assign any font query to sans-serif generic family if it has not received a generic family prior. A solution for this and description of the problem is mentioned here about Source Code Pro, it's probably not going to be an issue for emoji.

Lastly, although I'm not sure if any of these suggestions work

$HOME/.config/fontconfig/conf.d and $HOME/.config/fontconfig/fonts.conf, or their XDG equivalent paths, are defined in /etc/fonts/conf.d/50-user.conf, these are the official locations. The local one I'm not familiar with, perhaps its outdated/deprecated or distro specific.

Anyone else that comes across this, I've provided some more details about fontconfig and Chrome behaviour here.