Sunday, December 6, 2015

Re: Unintentionally closing Vim with many buffers open

On Sunday, December 6, 2015 at 10:37:14 PM UTC-7, Ben Fritz wrote:
> On Saturday, December 5, 2015 at 1:18:02 PM UTC-6, wolfv 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?"
> >
> > Thank you.
>
> Why are you using :q if you want Vim to stay open? Maybe :bd instead would suit your purposes better?

I didn't explain very well. This should clarify:

I usually work with one primary Vim open with multiple files in the buffers list.
Sometimes I will also temporarily open a few text files from the file manager, each file opened in its own Vim.
Then I quickly close all the temporary Vims by clicking the x in the top-right corner.
But sometimes I unintentionally close the primary Vim with the many files in the buffers list.
Then I have to reopen Vim and reopen all the files I was working on.
Is there a way to stop me from unintentionally closing Vim when the buffer list contains multiple files, like a configuration or plugin that prompts "Multiple files in buffers list, are you sure you want to close Vim?"

Some session managers give such a warning message.
But I don't want a session manager, I just the warning message.

I use ":source .fileList" to open groups of files that are frequently opened.
But that doesn't help when I close Vim with a one-off group of buffers.

--
--
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.

No comments: