Change:
Something about terminator and the way it uses python messes with your PATH setting, which interferes with Nix working properly. For example, echoing my path in xterm: But after launching into terminator, it looks like this: system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Unsurprisingly perhaps, but FWIW I can reproduce. Do you know if this is (or isn't) the behavior when using terminator in other environments? Anyway mostly wanted to let you know it's not just you :).
Hm, I guess with new buildPythonPackage it just doesn't run? And there is double wrapping, indeed…
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
I'll just go ahead and un-stale this. It's still an issue and I ran into it. The wrappers also set , which could probably also cause some trouble.
I marked this as stale due to inactivity. &rarr;
Still an issue
Also:
Hello, I have this same issue here.
I have the following issue: Within (e.g.) Gnome Console, my looks as it should: However, within terminator, it's messed up with several additional paths: (Both tested with bash.)
Yeah, that seems like the same issue. Problem is that it isn't straightforward to solve properly. If you want a slightly hacky workaround, some of the discussions on the equivalent kitty bug I linked above may help. Basically just use your shell init script to clean the terminator-only bits from . Something like: Should do the trick, I think. In very rare cases, this won't quite work right, such as if you start terminator from inside a , in which case it will obliterate the shell's additions, but it's pretty tough to get around that limitation here, and it's probably not a big issue. EDIT: scratch that, I'm being silly. will point to python, not terminator itself... you'd probably have to analyze to get a proper distinction. Like so:

Discussion:
, gtk3 , gobject-introspection , libnotify <ins> , makeBinaryWrapper </ins> , wrapGAppsHook3 , vte , nixosTests

file intltool gobject-introspection <ins> makeBinaryWrapper </ins> wrapGAppsHook3 python3.pkgs.pytest-runner ];

dontWrapGApps = true; <ins> # HACK: 'wrapPythonPrograms' will add things to the $PATH in the wrapper. This bleeds into the # terminal session produced by terminator. To avoid this, we force wrapPythonPrograms to only # use gappsWrapperArgs by redefining wrapProgram to ignore its arguments and only apply the # wrapper arguments we want it to use. # TODO: Adjust wrapPythonPrograms to respect an argument that tells it to leave $PATH alone. </ins> preFixup = '' <del> makeWrapperArgs+=("''${gappsWrapperArgs[@]}") </del> <ins> wrapProgram() { wrapProgramBinary "$1" "''${gappsWrapperArgs[@]}" } </ins> ''; passthru.tests.test = nixosTests.terminal-emulators.terminator;