Hi, PulkoMandy wrote:
Note that multi instance build of vim open new window on every call of "Open With... -> vim" menu item. Possible problem here is opening the _same_ file _twice_. :-)Just wanted to point that in this case (at least with the linux version of vim), it will complain about an existing .file.swp and ask the user if he wants to recover that. This is usually enough to point the fact that the file is already open.
Yes. The same behavior is observed with Haiku version. It prevent user from concurrent editing problems, but I'm speaking about consistency of UI behavior. Consistent solution in this case can be just activating window with already opened vim session for this file. But it works in such way only for single instance applications. :-) Looks like separate gvim binary executable can solve most of those dilemmas.
Kind Regards, S.Zharski.
