On Friday, October 6, 2017 at 9:57:28 AM UTC-5, daRAMA wrote:
> This was introduced somewhere between the first binary release of 8.0 and the 
> second one with patches 1-586 included and can still be reproduced in the 
> latest nighlty. Last tested with 1159.
> 
> To reproduce:
> 
> use a blank _vimrc with just "au GUIEnter * simalt ~x"
> gvim test.txt
> :w
> leave the instance open and start another vim: gvim test.txt
> 
> -> The second instance is opened and freezes (uses CPU and does not respond 
> to keyboard or mouse input)
> 
> 
> Use case for using two instances of vim on the same file: Do some coding in a 
> source file in the first instance and view the local changes in a source 
> control system (which launches a gvim -d file_in_working_copy 
> pristine_copy_of_file)
> 
> 

I'd guess it's waiting for your answer to a "swap exists" message. Does the 
second instance have anything else wrong with it (blank display, etc.)? What 
happens if you just press ENTER or type one of the swap exists answers 
(o/e/r/d/q/a)? 

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui