Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vim 9.0

vim.org

Post reply on HN
Print view View original

191–200 of 272 posts

Re: Vim 9.0

#191

Post by johncoltrane »

moelf wrote: post #154
mempko wrote: post #106

Earlier quoted context omitted.

This is untrue. Tons of development is done by others.

I mean: https://github.com/vim/vim/graphs/contributors https://github.com/neovim/neovim/graphs/contributors technically yes (by others too), but relatively, it's basically a one-man project

Vim has had a long life before being moved to GitHub and it still isn't developed the GitHub way anyway, so those graphs are meaningless.

Here are contributor lists I've gathered a few years ago from `:help versionX.txt`: https://gist.github.com/romainl/7b17317cc26a30116e51a3759022...

That's 600+ non-Bram contributors up to the fork that the Neovim team made disappear from their project when they removed the relevant files.

Re: Vim 9.0

#192

Post by threatofrain »

oblio wrote: post #83
azangru wrote: post #72

Earlier quoted context omitted.

Arrays start at 1?

Just like in math, and Lua doesn't do manual memory management so aligning stuff with memory addresses is not needed. They're both valid options and it's just about preference.

> Just like in math

I might be wrong, but I think math favors different starting indices based on the subject matter. I've seen Analysis textbooks favor 0 as the starting index. I don't think there's a clear argument for cultural transference from math.

I'm opposed to starting index from 1 because I think departure from very mainstream programming tradition should have a strong reason beyond preference, even if the de facto tradition appears equally capricious.

Re: Vim 9.0

#193

Post by johncoltrane »

givemeethekeys wrote: post #4

I'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's only a rabbit hole if you want it to be one.

Vim only has that reputation of needing a lot of config because too many newbies want to skip the learning phase and just jump in between two JIRA tickets. Of course you will need a lot of plugins and pre-baked stuff and hand-holding in that case!

The more sensible path is to learn Vim properly, and configure it as you go. It means that there's never a "take the week-end to configure Vim for React" moment: it's one line here, two lines there and it never really stops because you work with new languages and libs, etc.

As far as plugins. I can use Vim just fine without plugins or without my config but half of the plugins I use are written by me and tailored around my own needs so I guess those are the ones I need the most for my daily use.

Re: Vim 9.0

#194

Post by johncoltrane »

omoikane wrote: post #105

Lots of comments about Vim9Script here, but honestly the most noticeable change for me is the updated color scheme. Other changes: https://vimhelp.org/version9.txt.html

If you have any issue with them (well… beyond "I don't like it"), feel free to open an issue here: https://github.com/vim/colorschemes/issues

Re: Vim 9.0

#195

Post by pantulis »

Being an Emacs diehard myself, I very much enjoy when that other text editor sees a new major release.

Go Vim!

Re: Vim 9.0

#196

Post by jgb1984 »

the_duke wrote: post #3

I'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.

I use vim for a living. I need it to work. Always. Neovim in my experience hasn't been as stable, not by a longshot. Neovim adds things I don't care about (lua, lsp, treesitter) while taking away things that are essential to me (gvim, rock solid stability).

I see the neovim community holding up lua as a holy grail, rewriting entire vimrc configs just for the sake of it (even though a vimscript vimrc is much easier to read than a lua one) and rewriting rock solid existing vim plugins in lua, resulting often in a less stable and less feature complete plugin. But hey, it's now written in lua so it MUST be better!

Re: Vim 9.0

#197

Post by xigoi »

wruza wrote: post #91
capableweb wrote: post #20

As Vim9 comes alive, and Neovim community focuses on Lua plugins instead, it seems this release is finally the update that will put a hard branch on the two communities. Up until now, most plugins (except Lua-only ones of course) have worked in both editors, but it doesn't seem like Vim9 will be supported in Neovim, so I guess what people go with now, will decide what you might stick with in the future (unless you're…

My opinion must be marginal, but in my view neovim community took an IDE route anyway so maybe it is a good thing if they separate, provided there is a way to switch. Because when you have a function in bigpkg.tgz, no incentive exists to dedicate a smaller package to it, and that changes the entire landscape dramatically and may create political issues in it. I actually liked simple little plugins vim had back in the…

YCM is a plugin for Vim.

Re: Vim 9.0

#198

Post by usrbinbash »

kelnos wrote: post #145
margarina72 wrote: post #108

Earlier quoted context omitted.

open source mean the source is a open (and few other points described in [0]). Vim licence [1] is GPL compatible. It is fully open source. Open source does not mean the maintainer is under the obligation to add features, or integrate PRs. [0]: https://opensource.org/osd [1]: https://www.gnu.org/licenses/vim-license.txt

I think you mistake the parent's point. Vim's code is certainly open source (I don't think anyone disputes that), but its development model is not the one we've come to be comfortable with. Moolenar maintains an iron grip on vim, and controls what goes in (and what doesn't) much more strictly than many other open source projects. That is certainly his prerogative, but it's also the prerogative of others to not like t…

> but its development model is not the one we've come to be comfortable with

I am very comfortable with this model.

Re: Vim 9.0

#199

Post by xigoi »

sbf501 wrote: post #153
imron wrote: post #131

Earlier quoted context omitted.

Curious as to why you set ts but not sw?

because i've always found the vi documentation a bear to navigate. i don't know what shiftwidth is even for. here's the help for it: shiftwidth([{col}]) shiftwidth() Returns the effective value of 'shiftwidth'. This is the 'shiftwidth' value unless it is zero, in which case it is the 'tabstop' value. This function was introduced with patch 7.3.694 in 2012, everybody should have it by now (however it did not allow for…

This is the help for the shiftwidth function, not the shiftwidth setting. You need to do :help 'shiftwidth'

Re: Vim 9.0

#200

Post by xigoi »

u801e wrote: post #157
deadbunny wrote: post #71

Earlier quoted context omitted.

I have vim use the clipboard by default, with that said I still use the mouse to copy stuff now and then.

Depending on your OS, you could use visual line mode and highlight the text you want to copy. Then you can run: ' w !xclip -selection clipboard to copy the text to your clipboard. Macs have another program that works similar to xclip, but I don't remember what it's called.

What's the advantage of this command over "+y ?
Post reply on HN