Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify wording for running conda init #713

Merged
merged 8 commits into from
Sep 4, 2023

Conversation

marcoesters
Copy link
Contributor

Description

When asking whether to execute conda init, there is no explanation about what the consequences of the decision are. This can surprise new users to conda when their prompt is changed after restarting their shell.

Update the prompt to describe what is being changed and how it can be reversed before making a decision.

Checklist - did you ...

  • Add a file to the news directory (using the template) for the next release's release notes?
  • Add / update necessary tests?
  • Add / update outdated documentation?

@conda-bot conda-bot added the cla-signed [bot] added once the contributor has signed the CLA label Aug 23, 2023
Copy link
Contributor

@jaimergp jaimergp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is awesome, thanks! We should probably add it to the PKG UI too.

@marcoesters marcoesters marked this pull request as ready for review August 24, 2023 17:09
@marcoesters marcoesters requested a review from a team as a code owner August 24, 2023 17:09
@marcoesters
Copy link
Contributor Author

This is awesome, thanks! We should probably add it to the PKG UI too.

Good call! I expanded that text, too

preferred shell on startup. This will change the command prompt when
activated. If your prefer that conda's base environment not be activated
on startup, run `conda config --set auto_activate_base false`. You can
undo this by running `conda init --reverse ${SHELL}`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is ${SHELL} expected to be defined here or is it just a placeholder? I am assuming that it will be rendered in the SH installers but I am not sure about the PKGs. If it's meant to be a placeholder, that's ok too, just wanted to make sure it was not an oversight.

Copy link
Contributor Author

@marcoesters marcoesters Aug 31, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I expect this to be a literal ${SHELL}, not the rendered version. In the sh installers, I escaped the $ sign so that it doesn't get rendered.

marcoesters and others added 2 commits August 31, 2023 08:28
Co-authored-by: jaimergp <jaimergp@users.noreply.github.com>
@jaimergp jaimergp merged commit 3d38fd4 into conda:main Sep 4, 2023
15 checks passed
@marcoesters marcoesters deleted the sh-init-wording branch September 5, 2023 14:06
@github-actions github-actions bot added the locked [bot] locked due to inactivity label Sep 5, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla-signed [bot] added once the contributor has signed the CLA locked [bot] locked due to inactivity
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants