On Tue, Apr 14, 2015 at 08:49:50PM +0300, Nikolay Pavlov wrote: > NeoVim saves work in swap files. I also have habit of saving whenever > I pause which is recommended because OOM is less common then > > - Hardware power loss. > - Buggy VimL (or especially Python) with endless loop or deadlock. > (Vim with my configuration for some reason cannot stop `while 1 | > sleep 1 | endwhile` with `<C-c>` even though `vim -u NONE` can: this > is in case you want to say “there are no endless loops in VimL”; you > may also construct one using `catch /^Vim:Interrupt$/`.) > - Accidentally closed terminal emulator or Vim instance itself. > - `kill -KILL` send to a wrong Vim instance.
FYI, I've met several times of OOM condition in VPS with Linux, and every time when Vim becomes the victim a SIGKILL is sent to Vim, instead of Vim complaining there's no enough memory. > In neither of the above cases Vim OOM handling is going to work or you > will have any chances to save your work. So you can’t rely on yourself > being able to save your work in case of some troubles and suggested > course of action is either relying on swap files or saving your work > whenever possible. Both work in OOM case as well. > > [...] -- Best regards, lilydjwg -- -- 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.
