(In reply to comment #2) > qual="all" can actually already be used to test that a value is not set > because > it always returns true when there are no values to test. i.e. All zero values > match.
Hmm, that sounds like a bug though. IMHO we should drop such config entirely instead of ignoring the invalid element only or warn it at least, because there may be a typo and it's hard to track down when something behaves unexpectedly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/190848 Title: font in terminal does not resemble font in preview Status in Fontconfig - Font Configuration Library: Confirmed Status in GNOME Terminal: Fix Released Status in Ubuntu: Invalid Status in “fontconfig” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Invalid Status in “gnome-terminal” package in Ubuntu: Fix Released Status in “vte” package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-terminal When choosing a font for your Terminal profile, the preview in the font selector does not resemble the result in the Terminal window at all. Please reference the attached screenshot. The expected behavior is that the Terminal and the font selector preview look identical. Otherwise the selector is rather useless. To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/190848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
