Hacker News

I used to work for a large enterprise, and tried to get vim ‘approved’ for internal use. I remember this charityware clause caused our legal department to get tied up in all sorts of arguments about how we could be opening ourselves to liability if we used it without donating. It was my first lesson in navigating large company processes.

In the end I just kept quiet about the fact that it ships in all the Linux package repos.

(Just to be clear, I fully support what Bram did here)

Do I understand it correctly, but people donating to Vim, presumably for the support of the software, have their donations passed along to a charity supporting children in Uganda?

I'm not the target for your question (I distribute 0 plugins).

But Lua support in Neovim is the primary reason I moved over from Emacs. Elisp and Vim are both so heart sink for me.

That said I'd have preferred something other than Lua if I had the choice.

I love vim9script and write most of my plugins in it now unless I want something to work in the other vim as well, of course. Really happy to see it evolving and I'm particularly happy that tuple support has landed!

I think not adding new features frequently and keeping everything stable and working in the long-term is also meritorious. Vim is the same on my local machine, on my rpi, and on an Ubuntu 20.04 VM that I use for some proprietary software.

Also, I cannot think of an extension / new feature that makes sense as a part of Vim (if I want something more, I want a lot more. I don't want Vim to do a lot more, for the sake of simplicity and conformity, that's a job for vscode with Vim extension).

At the same time I wouldn't object to someone adding features to this program. But they have to try really hard to convince me to start relying on that feature (I wouldn't, because I would miss it on Ubuntu 20.04 and I will forget how I used to work without that feature).

I tried nvim a few years ago and honestly didn't find anything advantageous there. But since I had `:sh` in muscle memory and it was a bit (very?) different there I gave up on nvim.

I have also switched to nvim, but every release I consider moving back.

Honestly a lot of this is that I hate Lua. With so much of the infrastructure moving in that direction it's basically unavoidable. XDG support was honestly one of the things holding me back; I'm glad that this is finally fixed.

I don't think that will ever happen. They have already diverged in key ways. I'm more than happy with vim9 and where it is going, personally.

Has neovim settles on a UI yet?

NeoVim tossed significant amounts of legacy code (eg 8.3 filename support) and greatly improved out of the box default configuration. You cannot merge the two without upsetting one camp or the other. Vim wants to continue to be a stable platform that runs on 40 year old hardware. NeoVIM wanted to ditch the cruft that no longer makes applies.

I was happy with VSCode after decades of Vim because it felt light enough out of the box until Copilot starting showing up in every nook and cranny of the damn thing. I switch back to Vim last year.

> But where are the AI features?? Gonna get left behind!

Obviously vim doesn't need AI, but one feature I really wish vim had was native support for multiple cursors.

It's the feature that lured me away to Sublime Text in the first place many years ago, and it's a pre-requisite for pretty much every editor I use these days, from VSCode to Zed.

There are plugins, but multicursor is such a powerful force-multiplier that I think a native implementation would benefit.

Vim and its ilk have plenty of AI.

Actual Intelligence. It's connected to fingers/hands/arms/torso that is using it.

The announcement itself looks potentially AI-assisted, judging by the bulleted list style and redundant text under the "Charity: Transition to Kuwasha" section. But maybe some people just write that way.

I agree and I know what you're saying, but I'm pretty curious: how are people using AI with vim? I've seen some scripts for ollama but what are most people doing?

I made a vim extension where you describe the edit/action you want in natural language, and my ollama model thats trained on books like Practical Vim returns the key sequence and you can press e to execute without leaving vim. So you get automation help but also learn the syntax.

:please exit vim now

AISREIR

AI Should Rewrite Everything In Rust

Oopps, missed that. Now there is a v9.2.0 tag and a v9.2.0000 tag

The relevant release commit is, https://github.com/vim/vim/commit/e7e21018fc0b60c153c8e668f6... (at time of writing, two hours ago).

It seems they didn't publish the tag yet though.

Couldn't have come at a better time for those who are affected by their IT departments removing access to Notepad++.

Unless I'm misunderstanding the problem, Wayland is available on FreeBSD.

https://docs.freebsd.org/en/books/handbook/wayland

Why would they do that? When I started learning VIM more than 20 years ago, one of the main reason was that it (or vi) was already present and installed in every possible Linux system.

Yes, switch to Neovim. Seriously, no sarcasm. You can import your existing .vimrc at first, if you even care. I highly recommend kickstart or some other simple config scaffold.

do you really need that?

the scripting language is.. okay, but u have to try doing something practical in it, to get a feeling.

see my vimrc, being updating it since ~2000

https://github.com/svilendobrev/svd_bin/blob/master/qini/_vi...

There are the Practical Vim[0] and Modern Vim[1] by D. Neil

And the VimL Primer[2] by B. Klein

But Vim is a whole culture that starts with ed(1), the standard editor. You do edit based on line numbers and regex addressing and commands. Then there was ex(1) that added more features. vi(1) added a `visual` mode to ex(1), and some commands can now be done in relation to the position of the cursor. Vim is the improved version of vi(1), a lot more commands and a scripting language.

The plugin system is similar to everything that was unix at that time, relying on a variable like $PATH. Any path added to that variable (runtimepath for vim), should follow some patterns for subdirectories and the file will be loaded according to a certain logic. Plugin managers actually manage that variable and do a few things aside (isolating plugins, downloading from forges,...)

[0]: https://pragprog.com/titles/dnvim2/practical-vim-second-edit...

[1]: https://pragprog.com/titles/modvim/modern-vim/

[2]: https://www.oreilly.com/library/view/the-viml-primer/9781680...

Hey man, you’re not blocked. Read you loud and clear. Happy Valentine’s Day to you and yours.

In case you're wondering: I'm not blocked in this thread, but I was blocked in a thread about ICE. I told them to thaw out.

This is the perennial argument that IMHO is based on a fallacy. If the vim people suddenly stopped working on vim, it doesn't mean all their effort would go to neovim. People work on what they want to work on in open source. Also the two projects have very different goals/philosophies. The code bases have also gotten pretty different in architecture because neovim did a monstrous refactor. It's open source working as intended that we have both.

Could say the same thing about people working on neovim