Oh wow, didn't realize Fontconfig updated the cache anytime something starts. Did it always do that? Assumed this was left to things like gnome-settings-daemon or whatever. <div class="gmail_quote">On Mar 11, 2016 10:05 AM, "Keith Packard" <<a href="mailto:keithp@keithp.com">keithp@keithp.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Behdad Esfahbod <<a href="mailto:behdad@behdad.org">behdad@behdad.org</a>> writes: > We still be doing all the things we do right now. Just postpone computing > the charset to the first time it's actually needed, and add it to the cache > then. Might as well just stop updating the cache when applications start and insist that people run fc-cache. That would also solve the problem and not change how fonts end up getting matched. -- -keith _______________________________________________ Fontconfig mailing list <a href="mailto:Fontconfig@lists.freedesktop.org">Fontconfig@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/fontconfig" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/fontconfig</a> </blockquote></div>