Hi Bram Moolenaar, you wrote:

> 
> 
> Yes, well, there is a bit of a conflict about what Vim should do.  You
> told Vim to ignore files with a certain extension, and then you tell it
> to edit such a file.  In a new Vim this results in editing the file
> anyway, since there is nothing else to do.  In an existing Vim you get
> an error message, and keep the file you were working on.  I would think
> this is OK.  Is there a specific situation where you need Vim to edit
> the file you wanted ignored?
> 

I absolutely agree with what Tony said in sibling message. I expect that 
'wildignore' only affects file name completion. If I ask Vim to open this file 
explicitly, I know what I'm doing.

Also, note that the error message occurs even when I say

gvim.exe --remote-tab-silent <some file matching 'wildignore'>

and there isn't any gvim opened. So 

> In an existing Vim you get an error message, and keep the file you were 
> working on.

doesn't apply here well. There wasn't any file I was working on.

-- 
Alexei Alexandrov

Reply via email to