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

fix(nu): use the most recent starship init #3908

Merged
merged 2 commits into from
May 4, 2022

Conversation

davidkna
Copy link
Member

Description

The old nushell init approach caused the init only to update if the shell was opened a second time due to how nu handles sourcing (#3773 (comment)).

Thanks to @ajeetdsouza (thanks for notifying me!), there's a different approach that doesn't have this issue, by utilizing the nushell env file: nushell/nushell#4773 (comment)

The default env file also contains some prompt-related configuration, so using it for this seems reasonable. The supported nushell version needed to be raised to 0.61, because that version introduced the env file feature.

Motivation and Context

Closes #

Screenshots (if appropriate):

How Has This Been Tested?

  • I have tested using MacOS
  • I have tested using Linux
  • I have tested using Windows

Checklist:

  • I have updated the documentation accordingly.
  • I have updated the tests accordingly.

Copy link
Member

@andytom andytom left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants