On Mon, Apr 13, 2015 at 03:44:54PM +0200, Bram Moolenaar wrote: > > I included a few changes that were discussed on the neovim project. > I'm sure there are more, but it requires browsing through the issues and > locating the relevant ones. There is a lot of chatter on the issues. > Some have already been included.
Another thing to be aware of is that Neovim has changed some core functionality of Vim in ways that will cause problems with Vim if patches are naïvely backported. One such change that comes to mind is memory allocation. There are a set of functions implemented in Neovim (xmalloc, xrealloc, etc.) which exit if memory can't be allocated, rather than propagating the failure up to the caller. For example, their ga_grow uses xrealloc so there's never a need to check its return for success, but there is in Vim (which might be an issue in 7.4.690). I haven't been paying enough attention to Neovim to know what else may be relevant for backporting patches, but wanted to raise the issue that it isn't necessarily a "simple" task even once it's known that a Neovim change applies to Vim. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <[email protected]> -- -- 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.
signature.asc
Description: Digital signature
