| 19 Nov 2023 |
 Vika (she/her) | It's all so confusing and so annoying. | 16:39:40 |
| Vika (she/her) | ok, the gtk app chooser widget seems to be one thing responsible for collecting .desktop files in Nautilus's case, let's see what it calls to get a list of .desktop files
| 16:48:56 |
 Jan Tojnar | Vika (she/her): I would guess it has something to do with XDG_DATA_DIRS environment variable | 16:50:42 |
| Jan Tojnar | compare strings /proc/$pid/environ of Nautilus being launched by the different methods | 16:51:21 |
| Jan Tojnar | * compare strings /proc/$pid/environ of Nautilus launched by the two different methods | 16:52:19 |
| Vika (she/her) | Jan Tojnar That was my first thought! But... XDG_DATA_DIRS is almost the same between launching anything from wofi and my terminal, and both entries include /run/current-system/sw/share at the end, as they should.
| 16:54:26 |
| Vika (she/her) | In fact, almost the entire environment is the same! Sans a few variables GIO sets when launching an application using g_app_info_launch.
| 16:55:06 |
| Vika (she/her) | Specifically, these variables are XDG_ACTIVATION_TOKEN, GIO_LAUNCHED_DESKTOP_FILE{,_PID}, DESKTOP_STARTUP_ID and some minor variables like GPG_TTY (surely they don't affect this?). PATH is sometimes a bit different, but it's because of prefixes — the end is always /run/current-system/sw/share as expected.
| 16:57:49 |
| Jan Tojnar | Vika (she/her): I would try running it in terminal with XDG_DATA_DIRS=/run/current-system/sw/share and maybe some other variables cleared | 17:01:30 |
| Vika (she/her) | ...wait a second. | 17:10:27 |
