SoylentNews is people
SoylentNews
Vim 8.0 has been released. This is the first major Vim release in 10 years.
New features include:
- Asynchronous I/O support, channels, JSON
- Jobs
- Timers
- Partials, Lambdas and Closures
- Packages
- New style testing
- Viminfo merged by timestamp
- GTK+ 3 support
- MS-Windows DirectX support
Even if Neovim never becomes status quo in the vi world, has the competition at least given Vim developers a shot in the arm?
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
If more of us valued food and cheer and song above hoarded gold, it would
be a merrier world.
-- J.R.R. Tolkien
(Score: 2) by TheRaven on Tuesday September 13 2016, @03:32PM
A text editor that is mode based instead of a natural flow like every other text editor ever made
I've used vim to write four books (and over 150 articles, a couple of dozen papers, and I've long ago lost count of the amount of code). If I were starting again, I probably wouldn't use vi[m], because it really doesn't have a sensible learning curve. That said, I actually do think that modal editors are a good idea because the act of writing and the act of editing what you've written are distinct cognitive tasks. When I write with vim, I'm in insert mode and I type. When I've written a page or two, I enter command mode and then go and edit what I've written. The two distinct modes mean that I don't interrupt the flow of writing to go back and edit. I haven't done a formal user study, but I have found that articles that I wrote in more 'natural' text editors came back with a lot more changes from the copyeditor.
sudo mod me up