Re: Unintentionally closing Vim with many buffers open

On 2015-12-05, wolfv <wolfvolpi@gmail.com> wrote:
> Sometimes I unintentionally close Vim with many buffers open.
> Then I have to reopen Vim and reopen all the buffers I was working on.
> Is there a way to prevent this, like a plugin that prompts "Multiple
> buffers are open, are you sure you want to close them?"

How exactly do you create a session that fails to do this? I'm
not exactly familiar with all the ways to work with hidden
buffers, but I do know that in the most common case (multiple
files passed in on the command line), you get E173 if you try to
quit before editing all of them, and E162 if 'hidden' was
enabled and any of the others were unwritten.

Do you want it to refuse to quit even if the buffers aren't
unwritten? Do you want it to prompt even if you've typed "qa!"?

--
--
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.
For more options, visit https://groups.google.com/d/optout.