Florian schreef op vr 14-01-2022 om 22:52 [+0000]: > [...] I think the basic idea here is that the following should work: $ guix shell --pure some-terminal-emulator -- some-terminal-emulator # e.g., kitty # from inside the terminal: (e.g. nano) $ ~/.config/guix/current/bin/guix shell some-terminal-app -- some-terminal-app # Variation: run under sudo This works for kitty+nano, as you note, because kitty sets TERMINFO. It also works for kitty+'emacs -nw'. However, in some combinations things won't work: An example you noted is kitty+sudo+'emacs -nw'. This doesn't work for me either. This seems to be caused by 'sudo' clearing too much. As I understand it, this is only an illustrative counter-example, and not something that setting 'native-search-paths' could fix? This patch is about 'foot', so I tried running foot+nano, but that failed because I don't use wayland. Anyway, there seem to be a few options here: 1. patch the source code of 'foot' to set "TERMINFO_DIRS" or "TERMINFO" appropriately (I'm not sure about the exact difference) (or use wrap-program in 'foot'). The benefit of this above adding search paths, is that running 'foot' directly from the store could work (somewhat niche though). It would need to be investigated whether this works for your use case of setting 'foot-direct' instead of 'foot-xterm'. 2. modify 'nano', 'emacs', ... to add a "TERMINFO_DIRS" search path. A benefit of this approach above adding it to terminal emulators, is that this how search paths are supposed to be used AFAIK (adding an INFOPATH, LIBRARY_PATH, CROSS_LIBRARY_PATH, CPATH, ... search path to every C library that has 'info' documentation is rather cumbersome, instead INFOPATH ‘belongs’ to info readers, LIBRARY_PATH etc. to compilers, ...). A downside is that setting it here can be ‘too late’. E.g., in the "guix shell terminal" then "guix shell editor" example, the editor and terminal application are in separate profiles so guix doesn't set TERMINFO_DIRS 3. Like (2), but add it to the terminal apps instead. My order of preference: (1) > (3) > (2). Here, (3) would be a lot easier than (1) but almost as good, so maybe we could do (3) first and leave (1) for later? AFAICT It's not only 'foot' that is affected, should we do (3) for all terminal emulators that don't do (1) like kitty? Greetings, Maxime