I'm currently (ab)using the enterShell option to source a custom python virtualenv when I enter my development directory.
After updating devenv.nix, I find that my virtualenv is no longer activated. This seems to be a result of enterShell not running after reloading the devenv shell.
I'm currently (ab)using the enterShell option to source a custom python virtualenv when I enter my development directory.
After updating
devenv.nix
, I find that my virtualenv is no longer activated. This seems to be a result ofenterShell
not running after reloading the devenv shell.Is that by design, or an oversight?