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
Using vim list as source in pwsh will cause 'Command failed: type .....' #3517
Labels
Comments
setting $env:SHELL to cmd.exe fix the issue. Seems like there is logic error when escaping the path. powershell don't use ^ as escape character unlike cmd.exe |
kevyuu
changed the title
Using vim list as source in windows will cause 'Command failed: type .....'
Using vim list as source in pwsh will cause 'Command failed: type .....'
Nov 28, 2023
This happens to me intermittently. Closing vim and reopening it sometimes fixes the issue. (Perhaps something to do with the temp file name?) I have as yet not found a way to consistently reproduce it. |
Can you update fzf and fzf.vim to the latest and check if it helps? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
man fzf
)Info
Problem / Steps to reproduce
Type :call fzf#run({'source':['test1', 'test2']}) in neovim.
Error output:
The text was updated successfully, but these errors were encountered: