Simon McVittie

Updated to have three macros, here's a summary of using them correctly: ``` assert_cmpstr_free_lhs (g_strdup ("hello"), ==, "hello"); assert_cmpstr_free_rhs ("hello", ==, g_strdup ("hello")); assert_cmpstr_free_both (g_strdup ("hello"), ==, g_strdup ("hello")); ```...

`--socket=fallback-x11` is prior art for this, sort of (it's effectively `not-x11-if,wayland` in the syntax proposed here). In particular, anyone looking at implementing this should look at the implementation of `fallback-x11`,...

Would it perhaps be better to design a syntax for which any app with a Flatpak >= 1.16.0 dependency will be able to stop specifying `--device=all`, so that eventually (maybe...

> The goal here is to not have to wait for "being comfortable to depend on a flatpak new enough" I understand that, but I also don't want to still...

This is more difficult than you might think: at the moment Flatpak deals with a fixed, finite number of fonts directories (one for `$XDG_DATA_HOME`, one for `/usr/local` and one for...

Flatpak does not have direct control over the version or behaviour of GTK or libadwaita in Flatpak apps, so this is probably more likely to be a https://gitlab.com/freedesktop-sdk/freedesktop-sdk issue.

"Design" is a very general term, so I've retitled this to use the word "layout" to make it clearer what aspect of the design is not as expected.

> Gtk-WARNING **: 18:26:58.290: Locale not supported by C library This is the root cause of this issue. What are your locale environment variables set to? (`LANG`, `LANGUAGE` and anything...

What is `en_150`? I am not aware of 150 being a country code that is supported by glibc. Locale names normally look like `en_US.UTF-8` ("English as spoken in the USA,...

> How could I check whether the right Flatpak runtime extension is installed? If I understand correctly, `en_US.UTF-8` should be built-in, without any extensions, but `fr_FR.UTF-8` will require the `fr`...