nushell/nu_scripts
1
1
Fork 0
mirror of https://github.com/nushell/nu_scripts.git synced 2024-09-11 13:45:56 +03:00
Code Issues Packages Projects Releases Wiki Activity
1fb482ec31
nu_scripts/modules/virtual_environments
History
Darren Schroeder 92db3a88eb
update vswhere location for nu_msvs (#882) 
This PR makes the location of vswhere more programmatic by looking where
it's supposed to be located on the file system instead of relying on it
being in your path.
2024-06-18 09:19:02 -05:00
..
auto-venv Using def --env instead of def-env (#673) 2023-11-20 06:55:35 -06:00
nu_conda resolve several issues in nu_conda and nu_msvs (#872) 2024-06-07 07:36:00 -05:00
nu_conda_2 use typos for corrections (#833) 2024-05-08 06:47:54 -05:00
nu_msvs update vswhere location for nu_msvs (#882) 2024-06-18 09:19:02 -05:00
conda.nu Update conda.nu to use (sys host) rather than (sys).host (#839) 2024-05-22 06:35:50 -05:00
README.md use $env. instead of let-env (#543) 2023-07-01 10:40:16 +02:00
venv.nu Port before v0.60/virtual_environments (#849) 2024-05-26 12:38:00 -05:00

README.md

Virtual environment scripts

The scripts in this directory activate virtual environments for Conda environments.

Usage

The activation and deactivation commands are exported from the conda module.

> use conda.nu
> conda activate foo
[foo] > conda deactivate
>

The activate command also includes custom completions for the environment names. To disable the prompt changes (e.g., to let Starship include its own), set the environment variable CONDA_NO_PROMPT. To set it globally, add the line $env.CONDA_NO_PROMPT = true to $nu.config-path.

Limitations

(old text, not tested)

  • The "root_prefix" might not actually correspond to the correct path to the Conda envs. You can fix this for your setup by changing how the root prefix is found in the conda-env command.
  • Nested envs are not well supported. If you activate a Conda env while another one is activated, new elements will be appended to the PATH, but the other environment variables will be overwritten. There's no way to then restore the PATH to the state it was in before activating the first env (at least not with this script directly).