A similar thing also happened on OS X 10.11.4. After sourcing channelclose.vim, the message "Channel closed" appeared on vim in a second, and the cursor disappeared then.
Ten seconds later, another message "Channel closealarm after 10 seconds" came as expected. After that, it looked as if vim had hung, though vim came back to the normal mode by CTRL-L. Then, an operation on vim, say :e channelclose.vim, almost surely caused SEGV in five seconds. I repeated this experiment several times and got the same result every time. That "five seconds" was observed so persistently that I felt as if it were governed by a timer. Hopefully, this could be helpful. Best regards, Kazunobu Kuriyama 2016-04-11 3:56 GMT+09:00 Christian J. Robinson <[email protected]>: > On Sun, 10 Apr 2016, Christian J. Robinson wrote: > > On Sun, 10 Apr 2016, Bram Moolenaar wrote: >> >> Only on Windows? Have you tried enabling the log and see what happens? >>> >> >> Currently I cannot test on other platforms. >> > > For what it's worth, it happens under a cygwin build of Vim as well, > including a segv shortly after the close message. > > - Christian > > -- > Worry is the interest paid on trouble in advance. > > Christian J. Robinson <[email protected]> > http://christianrobinson.name/ > -- -- 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.
