On Di, 14 Apr 2015, Bram Moolenaar wrote: > It's weird to exit when running out of memory, that's not what users > want. It's easy to accidentally make a Vim script that consumes all > memory. It's making things easier for developers and worse for users. > Considering there are many more users than developers, that's a bad > choice.
Chances are high, your vim will be killed by the kernels OOM killer if you ran out of memory, so that does not make any difference in practice.¹ > > Anyway, sometimes it's suffucient to just see what code to change to fix > a problem. I'll keep an eye on the neovim issues and keep posting here, if I notice any problems that also affect vim. ¹) I have an open issue for my csv plugin that makes my vim killed by the kernel. If I have debugged that correctly, this is caused mainly by memline/memfile.c functions causing a massive allocation of memory on a :s command. VimL is mostly innocent and calling garbagecollect() does not help. Best, Christian -- Letzte Worte der Antiterroreinheit: "Die paar Terroristen sind keine Gefahr." -- -- 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.
