I appreciate @douglasdrumond's heroic effort to catch us up many patchlevels.
However, it would be best if we never got behind to such a degree that it requires a heroic effort to catch up. Here were are, already more than 60 patches behind. That's a LOT, even for MacVim (even though it's less than in recent months). To be clear, I'm not suggesting that there be more frequent *snapshots*. I don't use snapshots, I build from source whenever it's updated. I don't know any C, or anything about Vim's code, but if there's a way I can help keep on top of things, please let me know. Perhaps if there's a section on the wiki that explains which sections of the code are free of Vim/MacVim conflict, I and others could make github PRs for most Vim patches. Or perhaps @douglasdrumond can post the workflow involved in doing this. -Charles -- -- You received this message from the "vim_mac" 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_mac" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
