-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
[Windows] Cannot run in nushell #561
Comments
Hey 👋 I can't reproduce this on Linux, so it appears to be a Windows only issue. Are you able to run the command in nushell on Windows? |
Thanks for reply. This is no problem, even if I run the file in the current folder. The above problem only occurs when I use hover actions, it automatically |
That is not what I asked, sorry. Let me clarify: |
See also this comment:
To be able to handle paths with spaces, they must be quoted. This is the case for nushell too. |
Hi @mrcjkb , I found the cause of the problem finally. When nushell executes the command, the backslash in double quotes is treated as an escape character. So just replace the double quotes with single quotes or delete to solve the problem when create |
I've implemented a fix. But again, this is a bug in Nushell on Windows and should be reported there. |
I have been thinking this could be a neovim bug, specific to nushell and windows. I had a long discussion about something similar in a bug report in yazi.nvim here mikavilpas/yazi.nvim#366 If anyone finds some information about this (maybe a fix), I would appreciate a message, for example in this thread. Wishing everyone a nice weekend 🙂 |
@mrcjkb It works very well after updating. Thanks for your job, and thanks for @mikavilpas suggestions. |
Thank you for you job, it is a very usefull plugins.
Long story shart, I were using wezterm with nushell in windows systerm. when I run codes with hover actions, the terminal always fails to execute commands. It seems that the correct path cannot be opened. Normally, nushell does not need to
""
when executecd
commands.The text was updated successfully, but these errors were encountered: