I'd be willing to step in and help with keeping it up to date with vim patches. However I don't know C well enough to actually fix bugs, etc, so I only see myself as being able to help peripherally.
Speaking of this, I had been using the techniques in your Wiki to keep my fork up to date, however, something occured recently with a recent version of mercurial or hg-git where simply merging didn't work. It would attempt to re-merge the ENTIRE code-base, and I was unable to fix it. So my workaround has been just cherry-picking the new commits as they come in. On Wednesday, January 21, 2015 at 10:05:50 AM UTC-8, björn wrote: > Hi all, > > For quite some time now I have been unable to keep up with maintaining > MacVim and I've constantly been thinking that during the "next" > holidays I'll fix the outstanding issues. It is becoming apparent > that I'll never be able to find that time so I'm going to have to step > down as maintainer of MacVim. > > My apologies for taking so long to announce this. I did spend a few > days recently trying to fix some of the issues appearing on Yosemite > but I've not in that time been able to come up with a satisfactory > solution. This was perhaps the turning point where I realized I would > never be able to find enough time to keep up. > > If anybody is interested in taking over as maintainer, please let me > know and I'll fill you in on the workflow I've used to update Vim > patches and release snapshots etc. > > Björn -- -- 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.
