Skip to content
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

On Windows, "Got non-zero code from vifm: 255" #29

Closed
Melandel opened this issue Nov 11, 2019 · 1 comment
Closed

On Windows, "Got non-zero code from vifm: 255" #29

Melandel opened this issue Nov 11, 2019 · 1 comment

Comments

@Melandel
Copy link

Hello!

I work on Windows with vim8.1 (including patch 1-2197) inside a Powershell terminal (through Windows Terminal) run as Administrator.

I get the error "Got non-zero code from vifm: 255" whenever I try any vifm.vim command from within vim.

I noticed some messages appearing for a split second, indicating "Specified file was not found".

I have put the folder containing vifm.exe in the global Path.

My vimrc does not have any line related to vifm.

It has the same problem if I run vim from a simple cmd.

If I run vifm from the command line, it works. Same for :!vifm from vim.

How can I call :Vifm %:h from within vim without an error ?

@Melandel
Copy link
Author

I found the issue.

I had a line in my vimrc: set shell=pwsh.exe\ --NoLogo

I think it messed with the calls to tempname() (a story of forwarded slashes).

Commenting out that line in my vimrc solves the problem. I think adding the right 'shellslash', or having the 'shellcmdflag' start with a '-' might also work.

xaizek added a commit that referenced this issue Nov 29, 2019
Thanks to Melandel.

Fixes #29 on GitHub.
river4891 pushed a commit to river4891/vim that referenced this issue Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant