On Tuesday, April 14, 2015 at 10:43:11 AM UTC-5, Thiago Arruda wrote: > > It's easy to accidentally make a Vim script that consumes all > memory. > > If you see this often then you must be running Vim on a machine with > an extremely low amount of memory. This is not the case for most users > though, in the few years using Vim I never experienced this and I use > some pretty heavy plugins. Even if OOM was common due to bugs in > vimscript, it's not like the user will try to recover the current Vim > instance without exiting. The common course of action would be to exit > and remove the buggy vimscript program.
I know it's not common...probably even very rare...but wouldn't the common course of action actually be: 1. SAVE ALL WORK 2. Exit Vim 3. Remove buggy vimscript Step 1 is impossible if Vim just exits. True, it may not succeed if Vim attempts to handle the situation, either, but at least it can *try*. -- -- 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.
