Chip Campbell wrote:
> 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!")
>
> I've tried this with "s:" instead of <SID> and it still doesn't work.
>
> Hope y'all can duplicate this!
Note this remark in the docs of v:dying:
Note: if another deadly signal is caught when v:dying is one,
VimLeave autocommands will not be executed.
Can you check the value of v:dying somewhere, perhaps with a VimLeavePre
autocommand event?
--
MAN: You don't frighten us, English pig-dog! Go and boil your bottoms,
son of a silly person. I blow my nose on you, so-called Arthur-king,
you and your silly English K...kaniggets.
He puts hands to his ears and blows a raspberry.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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.
