-
-
Notifications
You must be signed in to change notification settings - Fork 220
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: cd
not working
#827
Comments
Yes, just double checked. |
Try with this:
|
Unfortunately, it's not working. I had Is there a way to get a verbose output of |
Yes, there's a log: https://dystroy.org/broot/community/#log |
Thanks, it says this:
|
You don't have other verbs than the one I proposed mapped to the enter key ? I'll have a deeper look and try on nushell but it won't be before a few days. |
No, no further mappings to enter, just the ones you posted in this tread. I just added this to be sure:
but it also is not working for me. |
I updated to nushell 0.90.1 and broot 1.34.0 and reinstalled the br shell function but the problem is still there |
I'm now on nushell 0.91. and broot 1.36.0 and the problem remains. These are the lines from the log where the
|
This launched
everything works fine. @FrancescElies @LudoPinelli @texastoland Is this behaviour to be expected from |
@Schweber I think this is spected because of nushell scoping rules, the environment changes inside your def function stay there and do not have side effects outside the funciton, try with
Try this two functions, cd-tmp will change directory of your current shell but cd-root won't.
Does this help? |
Yes, thank you for the explaination. I'll close this issue and make a PR to amend the documentation. |
I am using broot 1.32.0 with nushell 0.89.0 and applied the argument expansion to the
br
shell function from #821However,
:open_leave
doesn't work for me in nushell. I've set{ key: "enter", execution: ":open_leave" }
but if i press enter on a file/directory in broot, i'm back in the terminal without the folder having changed. Runningpwd
confirms this, so it's not a problem of the prompt not being updated.Using
{ invocation: "cd", key: "enter", execution: "$SHELL", set_working_dir: true }
"works" but this launches an additional instance ofnu
with the given folder so it's not a good workaround.What could be the reason for this?
The text was updated successfully, but these errors were encountered: