Alberto Garcia

By the way, there's another compatibility layer from SDL2 to SDL3, so you can even run Fuse with SDL3 using both layers, SDL1 -> SDL2 -> SLD3 :-) I just tested it again and it seems to work fine.

I'll have a look if I have time before the release, but for your information distributions (including Flatpak) are using Fuse with SDL2 thanks to the sdl12-compat compatibility layer, that allows SDL1 apps to use SDL2 without recompiling them. Of course we should ideally have native SDL2 support (or even SDL3!) but I confirm that sdl12-compat works just fine with Fuse.

Yeah it would be nice to make a new release, at least to fix bug #509: https://sourceforge.net/p/fuse-emulator/bugs/509/ Sergio, what do you think?

Hi, the Flatpak build of Fuse has three patches. Two of them have already been committed upstream as [039d7d] and [514389]. The last one is the one that changes the configuration file path: https://github.com/flathub/net.sourceforge.fuse_emulator.Fuse/blob/74570620c0a70f3608208bb53afdf94023c260a5/fuse-config-dir.patch Other than that it's a normal Fuse build.

Adding the FUSE_EMULATOR_CONFIG environment variable should be as simple as this.

A related idea (just mentioned in the mailing list) is to have a way to specify the path of the configuration file at runtime. An environment variable (FUSE_EMULATOR_CONFIG) would be the easiest, but a command-line option would also work.

Well, the patch was basically to merge upstream what I'm doing already in the Flatpak package, so it's not very sophisticated. Maybe I could have named it --enable-flatpak-build or something like that. Having proper XDG_CONFIG_HOME support would mean that the configuration file goes inside a subdirectory, something like this: $XDG_CONFIG_HOME/fuse-emulator/fuserc $XDG_CONFIG_HOME/fuse/fuserc $XDG_CONFIG_HOME/fuse-emulator/config $XDG_CONFIG_HOME/fuse/config Existing packages for Linux distros won't...

Here's the patch. We could also divide the number by 1000 and display seconds instead (since that's the actual unit used in the TZX file) but tzxlist uses miliseconds for everything else so maybe it's better to use it here too.