-
Notifications
You must be signed in to change notification settings - Fork 548
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
Bug Report for Zoxide v0.9.2 and Nu v0.87.1: Deprecated Commands #650
Comments
This is already fixed in #632 |
Sorry totally oversaw that, thanks! |
This didn't make 0.9.2, or the wrong source is on crates.io. nutshell 0.88 released today, and zoxide is now breaking my env.nu, and general shell configuration on launch. Can we get a new release? |
In the meantime, an alternative is to not dynamically generate the file, and instead generate it once, fix it manually to use the new syntax and only source it in your nushell config |
Or just comment it out and not use zoxide in my nu sessions as it isn't currently my primary shell (due to things like it's shifting syntax) and wait for a new zoxide dot release. |
Summary:
When using Zoxide version 0.9.2 in conjunction with Nu version 0.87.1, the user encounters deprecated commands, specifically def-env, resulting in error messages. The affected lines are in the file "~/.zoxide.nu" at lines 25 and 36. The error messages suggest using def --env instead.
Steps to Reproduce:
Expected Behavior:
The commands should not be deprecated, and users should not encounter errors related to deprecated features.
Actual Behavior:
Users receive error messages indicating the usage of deprecated commands (def-env), which are scheduled to be removed in version 0.88.
Error message:
Environment:
The text was updated successfully, but these errors were encountered: