If this problem has consequences (vim dying in the middle of your work can be bad), if you build your own vim a workaround is to modify os_unix.c in the x_error_handler function, to replace the preserve_exit() call with
g_print("%s", IObuff);
or just comment out the preserve_exit() call. I have used this workaround for a BadWindow error for about a decade, with no ill effect.
Regards, John Little
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/28ea59ef-941a-41eb-a700-7180ae0a7cbd%40googlegroups.com.
No comments:
Post a Comment