On Mon, Apr 4, 2016 at 10:13 PM, Bram Moolenaar <[email protected]> wrote: > > I have been wondering if the next release should be called 7.5 or 8. > We have quite a few new features, but not that many as with the Vim 7 > release. Well, that was a big release. I think the most important > addition since then is persistent undo in 7.3. Now we have more new > features than in 7.3 or 7.4. 7.1 and 7.2 were mostly bug fixes. > > I have made a list of the most important improvements compared to Vim > 7.4. I might still be missing some (let me know!). > > Also, now is a good time to check out the new features, we can still > make changes. Especially the Channel, Job and timer support. Once the > release is out we can't really make changes that break backwards > compatibility. > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > Asynchronous I/O support, channels ~ [...] > Jobs ~ [...] Both seem intimately related. I don't (yet) use this but from the number of patches affecting it it looks like a big feature.
> Timers ~ [...] This may be small stuff compared to the rest but my little finger tells me it's going to get important in the future. > Partials ~ [...] Deepening the already existing Funcref concept, making it more general. > New style tests ~ [...] I don't write tests myself, but this has already generated a host of "new style" tests, i.e. tests written in vim-script with assertions, rather than in normal-mode Vim code with a preset "correct result". This obviously is already big in terms of applications. > Window IDs ~ > > Previously windows could only be accessed by their number. And every time a > window would open, close or move that number changes. Each window now has a > unique ID, so that they are easy to find. I haven't yet played with this, but it also seems an important enhancement. Oh, and there is still some other stuff, whose exact introduction point I didn't notice at the time, such as the 'emoji' option which was featured repeatedly in recent vim_dev posts. > > > Vim script enhancements *new-vim-script-8* > ----------------------- > > In Vim scripts the following types have been added: > > |Special| |v:false|, |v:true|, |v:none| and |v:null| > |Channel| connection to another process for asynchronous I/O > |Job| process control > > Many functions and commands have been added to support the new types. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > -- > hundred-and-one symptoms of being an internet addict: > 223. You set up a web-cam as your home's security system. > > /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ > /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ > \\\ an exciting new programming language -- http://www.Zimbu.org /// > \\\ help me help AIDS victims -- http://ICCF-Holland.org /// All in all, my impression is that this release will differ much more from 7.4.0 than the latter differed from 7.3.0. OTOH, 6.0.0 was before my time, and of the differences between 6.0.0 and 7.0.0, some (Unicode support? vimgrep?) enjoyed a v6 minor release, while others (e.g. tab pages) did not, so what are we to use as a standard for comparison? 7.0.0 "final" (I don't count alpha snapshots) vs. the last 6.x.0 minor or vs. the first 6.0 major release? IMHO this future release has enough going for it that calling it 8.0 won't sound out of place (or a case of "marketing boastfulness"), but I've also seen the opposite opinion expressed while rapidly scanning the previous responses, and while "feeling the field" is useful, I think the final decision will rest with Bram alone, and I am prepared to abide by it, whatever it finally will be. Best regards, Tony. -- -- 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.
