Alexei Alexandrov wrote:
Hi A.J.Mechelynck, you wrote:
Exe or dll files are usually binaries (which shouldn't cause E479
however); and unlike cmd.exe when "executing" them, Vim doesn't lookup the
PATH for editfiles.
1) Are you sure the directory containing the editfile was current? If it
wasn't, you should mention the path to the file on the command-line.
2) If the file's dir was current, try using
gvim --remote-tab-silent +"set bin" bjam.exe
Note: The Vim help is not very explicit: I'm not sure if the additional
parameter should be
+"set bin"
"+set bin"
or
+set\ bin
If one of them doesn't set 'binary', try another variant.
The key in the bug report is that error is reproducible only with
--remote-tab-silent. I'm not sure why the advices above can have different
behavior with this option.
I was trying to find something that could be specific to these files (and
which the other files, which don't exhibit the bug even with
--remote-tab-silent, wouldn't have); if you read what I wrote, you will have
noticed that I kept the --remote-tab-silent. If you don't try anything, you
won't find anything. If you try something and it doesn't work, you will at
least have "closed some doors", as detectives say. In any case, it is always a
good idea to set 'binary' whenever you are editing (or even viewing) a binary
file.
You said you noticed a correlation between the bug and the editfile's
extension being in 'wildignore'. Now maybe that's something which deserves
looking into. I don't know the Vim C code well enough to come with a solution,
but maybe Bram (or someone) will.
Best regards,
Tony.
