-
Notifications
You must be signed in to change notification settings - Fork 546
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
Error with nushell 0.83.0 #595
Comments
Solution is following:
|
For now I just removed this check in if statement. So it becomes: |
Thanks for this. It was throwing a weird error when I tried the first fix, adding |
as said in #596, this issue has been fixed in nushell/nushell#9816 and should be released in a patch release soon 😌 |
add a try block around init zoxide in .env and change the load file temporarily with fix from: ajeetdsouza/zoxide#595 ajeetdsouza/zoxide#595 (comment) aswell as change let-env to $env.
waiting for fix to ajeetdsouza/zoxide#595
It looks like original if check works fine now with updated nushell 0.83.1. |
Awesome, closing this then. Thanks! |
I've updated to nushell 0.83.1 and still seeing the error related to I thought maybe I could just edit Solution was to disable to init script from running every time. I guess if the |
@charlesroper yes, the nushell 0.83.1 release notes explicitly note that let-env won't return That one is pretty simple to update though with a simple replace/update. |
- ajeetdsouza/zoxide#595 Reinstalled zoxide with 'cargo install --git https://github.com/ajeetdsouza/zoxide' instead of ''brew install zoxide' or 'cargo install zoxide' fixed the issue of 'zoxide init nushell' containing the now deprecated 'let-env', even though it is fixed in the main branch: https://github.com/ajeetdsouza/zoxide/blob/main/templates/nushell.txt
@charlesroper |
@ajeetdsouza |
Released in 0.9.2. |
For anybody else coming here, make sure |
The project is not well-adapted to the latest version of nushell, version 0.83.0, and it displays the following error:
The text was updated successfully, but these errors were encountered: