Terminal running in environment about nix-env-selector HOT 5 OPEN

Another simple solution I found is to add a custom terminal profile. Here's an example you can drop into your code-workspace config:

{
	"settings": {
		"terminal.integrated.profiles.linux": {
			"Nix Shell": {
				"path": "nix-shell",
				"icon": "terminal-linux",
			},
		},
		"terminal.integrated.defaultProfile.linux": "Nix Shell"
	}
}

There is that couple second delay when you open a window from running nix-shell but it's not nearly as bad as waiting for it to open then running nix-shell yourself :)

from nix-env-selector.

Please correct me if I'm wrong, but a workaround could be to set up direnv in the project folder. That way, every time one enters the project directory via the VS Code terminal, nix-shell is started. At least it seems to be working for me.

from nix-env-selector.

This should rather be an option, as sometime you want to get out of the nix-shell to edit it and debug it.

from nix-env-selector.

An idea, document the behavior. I'm rather new to nix pkgs. My first thought that the extension was broken since the packages weren't available in the terminal.

from nix-env-selector.

this is a good workaround for now, but I think it would still be good for the plugin to somehow include this functionality

from nix-env-selector.