-
Notifications
You must be signed in to change notification settings - Fork 573
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
nushell breaking changes #630
Comments
Thanks this was really helpful! |
nushell will deprecate `def-env` and use `def --env` in the next release(0.87) Currently `def --env` is already available in latest version (0.86) Relative: ajeetdsouza#630
After updating to the new nushell 0.87.0 release, I encountered the following error when opening a new terminal:
I noticed that there are already two PRs that address this issue: #632 and #642. |
@lpnh Just FYI - This last part has nothing to do with zoxide.
$env.config.cd.abbreviations was removed from nushell in favor of using our path completions that work similarly now. You just need to comment that out of your config.nu (or remove that part). |
As far as I can see the only two places where zoxide needs to be updated are Lines 42 to 61 in 073500c
I think it's just a matter of replacing |
Hello. I have notice there is a fix commit "f537a4e6d2f8c2eb84c63f79e290a6d1b16eeb71" in zoxide. How can I install this dev version of zoxide? |
$: brew install --HEAD zoxide
Error: No head is defined for zoxide |
When will this be pushed to crates.io? Currently having to install from git. |
Nushell has just published their update, removing |
For now I'm just using this in my env.nu zoxide init nushell | str replace "def-env" "def --env" --all | save -f ~/.config/nushell/modules/.zoxide.nu |
This commit should be reverted once ajeetdsouza/zoxide#632 is released.
Hey, the list of incompatibilities grew longer.
Which can also be added as a workaround because there are two places where
nevermind. I found the PR |
This reverts commit 9128641. zoxide v0.9.3 has been released.
Heads-up @ajeetdsouza, With nushell/nushell#10566 we will deprecate the
def-env
syntax in nushell. Our next release 0.86.0 on Oct-17 will allow both old and new syntax but the next release, 4 weeks later, will produce a warning. The new syntax isdef --env
.The text was updated successfully, but these errors were encountered: