Christian Brabandt wrote: > Hi Charles! > > On Do, 26 Feb 2015, Charles E Campbell wrote: > >> Hello! >> >> I've attached a script which illustrates the problem. >> >> vim -u NONE -N prblm.vim >> :so % >> :q (in the gvim that's showing prblm.vim, NOT the remote gvim) >> >> Behavior: >> >> * a remote server gvim shows up (this happens) >> * a message "verify its working" shows up in the server's message >> line (this happens) >> * both the client vim quits (this happens) AND the remote server >> gvim quits (this does NOT happen) >> >> The remote server gvim should quit because of an autocmd VimLeave event: >> >> au VimLeave call <SID>RemoteSend(":qa!") > You are missing the pattern for the VimLeave autocommand. > I believe it works if you provide one (or *) > Thank you, Christian. Sorry about the noise. It was a late night brain freeze
Thanks, Chip -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.