Earlier quoted context omitted.
I've been using vi/vim on a near daily basis for 34 years now and this is the only thing I put in ~/.vimrc: set tabstop=4 set expandtab set shiftwidth=4 " or 2 or whatever set shiftround syntax on EDIT: Just for some fun archeology, I google searched on the 3rd line, 'set shiftwidth=4 " or 2 or whatever' because I very dimly recall copying most of my standard set (minus the syntax on bit) from someone else a long lon…
" My vimrc from 1994 to about 2000 set et set ts=4 " Added this circa 2000 syntax on " Added this ~2013 let g:solarized_termcolors=256 set background=light colorscheme solarized
Vim 9.0
131–140 of 272 posts
Re: Vim 9.0
#132Re: Vim 9.0
#133Re: Vim 9.0
#134Earlier quoted context omitted.
Since Vim has been Bram’s project for decades, I have some empathy for him to want to continue doing things his way and to not compromise on that. It may have taken Neovim to convince him that certain features are important, but that doesn’t mean he has to like how those are realized in Neovim. Open source is freedom, and I believe it’s okay for him to make use of his freedom to design things in his way, even if the…
I don't disagree with anything you've said but I would personally take this line of argument a step further. I think Bram learned from the neovim fork. Neovim bolstered the existing lua support by reducing the impedance mismatch between the lua language and the vim host. A lot of people enjoy writing lua more than vimscript but the value-add hasn't proved compelling enough for people who didn't mind vimscript. The of…
Much of that is "just" the runtime files (things that define language syntax, etc), which are x-compatible (broadly) between nvim and vim. Seems it would be foolhardy to just re-write all that in lua, "just because".
Re: Vim 9.0
#135I'm curious how many users are now using vim versus neovim. I switched a few years ago,and ever since Lua plugin support the Neovim ecosystem is thriving.
Debian switched back from Neovim to Vim as the default “vim” in Buster(?), so I switched back along with it.
Really surprised to see /Debian/ of all things pick Neovim, especially years ago when it was even newer, as a default over Vim and would love to see the discussion around it. It would have been ~v0.2 for Stretch and ~0.3 for Buster, and only a year old during Jesse.
Re: Vim 9.0
#136Earlier quoted context omitted.
Well, Bram is the author of the parent project, he doesn't have any obligation to make it compatible with the derivative.
Vim has been around long enough that I'd argue it's just as much owned by the community at this point.
Re: Vim 9.0
#137I'm curious: - How deep a rabbit hole do most people go down when setting up their vim / neovim environment? Apart from setting up a preferred color and language specific tab spacing and highlighting, I don't need more, but I've seen some pretty fancy setups. Out of the different plugins, which would you never operate without?
It depends what kind of person you are, how much energy you want to invest, how much patience you have for stuff that isn't the code you're writing, how much you enjoy editing itself, etc. I have a quite extensive setup ( https://github.com/Julian/dotfiles/tree/main/.config/nvim ) which I built up over 10+ years, indeed sometimes including sitting there for an hour or two and just investigating plugins or writing som…
Re: Vim 9.0
#138Earlier quoted context omitted.
Vim has been around long enough that I'd argue it's just as much owned by the community at this point.
You can argue that, but what would that even mean? Forceful requisition of his website and private keys?
Re: Vim 9.0
#139Earlier quoted context omitted.
Although I am currently tip-toeing on NeoVim, I still feel this is a horrible break-up. Yes, Open Source simply allows you to branch whenever you're unhappy with the original but this comes at a cost for the community. The cost of having two diverging programs to deal with. In this case, the motivation was simply insufficient. Some people wanted vimscript+lua instead of vimscript. They felt the code was too difficult…
Neovim has already been very productive by giving Vim some good competition and in so doing having better features come out in Vim. To me it doesn't make sense to 'hate' neovim for wanting to develop features that they tried to have in Vim but couldn't due to the main developer stalling it.
Re: Vim 9.0
#140Earlier quoted context omitted.
Well, Bram is the author of the parent project, he doesn't have any obligation to make it compatible with the derivative.
Vim has been around long enough that I'd argue it's just as much owned by the community at this point.