Dashes instead of underscores in command comparisons #816
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Awesome thanks! |
ayax79
pushed a commit
to ayax79/nushell.github.io
that referenced
this pull request
Jun 26, 2024
I wasn't sure if this was on purpose or not but the conda environments were simply "activate" and "deactivate" instead of "conda activate" and "conda deactivate" as they would be normally in bash/zsh. Due to the potential name conflicts I think it's better to leave these as the more specific `conda activate` and let the user define an alias in their file with `alias activate = conda activate`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I know nothing about nu, but https://www.nushell.sh/commands/docs/is-empty.html and https://www.nushell.sh/commands/docs/with-env.html spell them with dashes.