On Sat, Mar 4, 2017 at 10:10 PM, Christian Brabandt <cbli...@256bit.org> wrote: > On Sa, 04 Mär 2017, Bram Moolenaar wrote: > >> >> Christian Brabandt wrote: >> >> > On Di, 28 Feb 2017, Bram Moolenaar wrote: >> > > But also testing fdm=marker requires more work, I'll leave that for >> > > now. >> > >> > Are you sure? I think adding a :set fdm=marker and the rest should be >> > the same, foldmarkers will then be set automatically. >> >> Hmm, I thought markers would have to be added to the text. But it >> appears the default marker and comment work. So that's easier than I >> thought. > > I initially tried the test with fdm=marker (without noticing at first) > and wondered why it worked. So I noticed that the marker test should > work easily > >> I wish they would have made it easier to make patches work for both. >> Now patches have to be written and applied twice, for no good reason. > > Yeah, that was what I thought as well. I asked him for putting the patch > right here upstream, but apparently he did not want that (for whatever > reason). At least he later also provided a Vim compatible patch.
Neovim devs have gone to great effort to merge thousands of Vim patches (meanwhile marking the noise-commits related to TINY build as N/A, since the TINY build is not tested against before committing to master). Now, Vim devs complaining about formatting for a few cases where we didn't do double-work, is remarkable. By the way, what are the technical (not emotional) reasons that prevent Vim from adopting the Neovim tree, going forward? I'm sure there are a few, but listing them out would be very useful. --- Justin M. Keyes -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
