-
Notifications
You must be signed in to change notification settings - Fork 1.1k
"Can't open file" error on Windows 10 #1906
Comments
What version of syntastic are you using? |
The last one:
Well using the fix apparently this:
|
Plase leave it at the current master HEAD. Edit your vimrc, and set |
The output based on your instruction:
This is the intended output I wanted to post first. Had a typo in 'let g:syntactic_debug = 1' ... |
This:
means you have to use slashes when setting
|
Please stop posting screenshots, thank you. They can't be referenced, and can't be indexed.
According to your logs syntastic doesn't get to see that. |
Syntastic did see it, not sure if 'expand' did the slashes replacement. Anyway syntastic still complains, when I write out the path:
Good point!
I meant "... via Pathogen" |
What happens if you run :echo system('pylint -f text --msg-template="{path}:{line}:{column}:{C}: [{symbol}] {msg}" -r n tmp/code/python/vim-as-a-python-ide/demo.py') in the exact same context as above? |
|
Your |
I did the research #772, #814. The following pylint option (if called from inside vim) causes the error:
Replacing the quotes in line 53 in pylint.vim did the trick:
|
This shouldn't change anything if your |
Well, it made the difference for me. However, in the end its a windows machine...
|
Right: it makes a difference because of your |
Seems to be similar to #979:
Unfortunately the fix didn't worked out for me!
Btw the output in the screenshot is after having set 'let g:syntactic_debug = 1'
I have no clue what is the purpose of the "missing file". Either way, I cannot find that file on my hard drive.
The text was updated successfully, but these errors were encountered: