It's a joy to read such a polite newsletter. Friendly towards to original source. Friendly and open as a community. Everythings seems well organized and distributed. Well done!
Also thanks a lot for the tool, I use neovim almost daily.
Newsletter #7 - Summer of Road
11–20 of 36 posts
Re: Newsletter #7 - Summer of Road
#12Earlier quoted context omitted.
I read that article and didn't get a good handle on any features that would motivate a transition from Vim. Any links you could provide?
Same here. Scrolled through it and the only thing I got is that there is a command called ":smile" which is not worth switching to me. Doesn't mean there is none, it's just hard to find.
:smile is a vim command that was introduced in the new version of vim, I'm not sure but it seems like they are making fun of it.
There's always been a bit of hostility between the neovim people and Braam, last being the fact that Braam finally implemented jobs in Vim 8, but using a different API than neovim.
Re: Newsletter #7 - Summer of Road
#13Is neovim packaged for distros?
Re: Newsletter #7 - Summer of Road
#14Re: Newsletter #7 - Summer of Road
#15Re: Newsletter #7 - Summer of Road
#16Is neovim packaged for distros?
I've been using Debian's neovim package for the last several months, but I use the unstable repositories.
I think it'll be officially packaged in the next Debian release though.
Re: Newsletter #7 - Summer of Road
#17Earlier quoted context omitted.
:term to run a terminal in a vim window. Also, much more sensible defaults.
Cool, but why?
Avoiding multiple levels of window management, when you want to edit multiple files and have one or more additional terminals available.
For instance, I've used this to edit a manpage with a live preview to the side in another window. Doing the same thing with screen would require running vim inside screen, and doing window management with both screen (for terminals) and vim (for everything else).
Re: Newsletter #7 - Summer of Road
#18For better or worse they awoke the sleeping giant[1]. Curious to see how things play out with the fork (i.e. will vim users stay put or move on to neovim in the coming months/years). [1] https://github.com/vim/vim/graphs/contributors
I'm not sure how it could be 'for worse'? Even Neovim benefits from the uptick in Vim patches, because they actually merge many of them into Neovim. So it seems like it can only be a good thing. Better editors for everyone.
That's one way it could play out, but that's not the way it did play out. Vim ate Neovim's lunch because they took so long to create a release that Vim was able to copy their best features. Worse yet, they did this in a way that is not compatible with Neovim. There is a chasm between Vim and Neovim that is growing, and the incentive to cross it is shrinking.
As someone who has watched closely Neovim's development since its announcement, and used it as my daily text editor for literal years, I feel sad to say that it is early-stage vapourware. They kicked vim into action, then vim kicked them out of it.
Re: Newsletter #7 - Summer of Road
#19Earlier quoted context omitted.
I read that article and didn't get a good handle on any features that would motivate a transition from Vim. Any links you could provide?
:term to run a terminal in a vim window. Also, much more sensible defaults.
An embedded terminal emulator is exactly what Neovim should not have.
Re: Newsletter #7 - Summer of Road
#20Earlier quoted context omitted.
:term to run a terminal in a vim window. Also, much more sensible defaults.
Cool, but why?
I like being able to have a vim window that has a terminal in it, there are some cases where I just prefer to have it in my terminal environment rather than switching to another real window. Mostly this is for things where I want to be in the same directory as my editor to run greps through my source, etc...
It's also nice sometimes to do something and then be able to search through the history with "/". At times I've then gone back and cut and pasted between the terminal output and a document I was working on, rather than using my window manager cut and paste.
I was, however, fairly surprised that I could no longer ":sh" out to run something. Had to get used to ":term" or ":spl term://bash".