Should nu_conda.nu use CONDA_DEFAULT_ENV instead of CONDA_CURR?
Open
Nobody has claimed this yet.
- Dominant language
- Nushell
- Stars
- 1.3k
- Forks
- 323
- Avg merge
- 2h 55m
- Merged PRs (30d)
- 3
Description
I'm using Starship and Nushell on Windows. I noticed that Starship uses CONDA_DEFAULT_ENV as the default environment variable for Conda. Would replacing CONDA_CURR with CONDA_DEFAULT_ENV be a better choice?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with nu_conda.nu and inspect how the script reads CONDA_CURR when displaying the active Conda environment. Compare that variable with CONDA_DEFAULT_ENV in the reported Starship behavior, then verify that the script uses the intended environment value on Windows and does not regress existing Conda prompt output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100