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(init): Change Nushell init for nu 0.60 #3773
Conversation
Nushell 0.60 has been released! |
I just tried these new instructions on macOS but they do not work as the config file is read from |
It might be worth checking issue nushell/nushell#4773 which was opened for zoxide but I believe will apply to starship and the updated instructions from this PR The TLDR is that the ref.: https://www.nushell.sh/book/thinking_in_nushell.html#parsing-and-evaluation-are-different-stages |
@jfchevrette Thanks for the suggestions. |
def starship_prompt [] {
# jobs are not supported
# status is not supported
starship prompt --cmd-duration $env.CMD_DURATION_MS
}
let-env PROMPT_COMMAND = { (starship_prompt) } Maybe you can try this one? |
@chen244 Given the high likelihood of future changes to the shell, I would rather avoid that. |
@matchai - thanks for working on this fix. I made a comment about Nushell's parser/evaluator separation. For that init step, since it won't run before the |
|
@davidkna - oops, I should have tagged you for ^ |
This is part of the PR. |
Description
This PR updates the nu init for the upcoming v0.60 release.
directories-next
is also replaced bydirs-next
again to match nushell behavior.Motivation and Context
Closes #1716
Closes #3526
Screenshots (if appropriate):
How Has This Been Tested?
Checklist: