conda.nu: Support for --prefix flags

[LordFckHelmchen]

Currently, the conda.nu script supports named conda envs. But it would be great if we could get support for local conda environments (aka created with --prefix flag, like conda env create -p .venv/)

[fdncred]

Feel free to tweak on the script to help with that.

[Tiggax]

I can try to update the script to use envs instead of the current envs_dirs. I'd just like to know how it would be better to work? Some of current options:

• when typing conda activate should it try to autocomplete to base ... .venv where you can select the .venv to use the local virtual environment
• typing conda activate and not selecting anything would check first for any virtual environment in current directory and if not finding anything default to base

[LordFckHelmchen]

Hey @Tiggax , thanks for taking it on. My workflow is very focused on having all environment specs within a repo. So we check-in the environment.yml and always create the venv/conda env locally within the checked-out repo. Since I normally work with nu, when starting to code, I always have to switch back to CMD just to be able to activate the conda env and work with it. Just as a background.

The activate script should just behave as conda does it. I think they detect if the argument after the activate is a path or a name by looking for separators, e.g. try conda activate .venv (tries to resolve .venv as name) vs. conda activate .venv/ (tries to resolve .venv/ as path). I think that would be the easiest solution... And yes, @fdncred, if my nu shell scripting skills would be better, I would contribute, but I'm literally at 0