Ken Odegard

For `conda activate` to work properly it needs to be initialized as a shell function. This is done by the code injected into your user profile (e.g., `.profile`) when you...

Based on what I see you're doing, everything is working correctly. The `conda` command is a shell function that processes activation subcommands (e.g., `conda activate`) differently from other subcommands (if...

@Userfound404 thanks for working on this however all of the subcommands are auto documented via the `argparse` implementation, this is done via the following: https://github.com/conda/conda/blob/f221170a6fc5c3fb2213f1494c3ac17531c10b7d/docs/source/commands/create.rst?plain=1#L4-L10 To see the rendered docs...

well what do you know this has been completed, see #13792!

Fair, so something generic like detecting that the user specified the build string and upon failing suggest dropping the build string requirement?

The effort to introduce better error reporting via the libmamba solver may aid here? https://github.com/conda/conda-libmamba-solver/issues/102

Another example of `conda` vs `conda env` confusion: https://github.com/conda/conda/issues/11651

On Windows, Miniconda is bundled with the "Anaconda Prompt" (there are both CMD and PowerShell variants) which initializes conda for you to avoid these issues. Alternatively to using the "Anaconda...

> I'll try to keep in mind, because now that I was forced to set the variables into the environment PATH, I can't seem to be able to get rid...

`conda create`, `conda install`, and even `conda update` all support a `--download-only` argument which downloads the package to the package cache. You can find your package cache by running `conda...