12 ms·
Vim 9.2
- jmclnx 8mo agoCongratulations! >Full support for the Wayland UI I really hope they never deprecate X11 support :) I doubt they will, but if they do, it will leave the BSDs without a good alternative.
- zenoprax 8mo agoUnless I'm misunderstanding the problem, Wayland is available on FreeBSD. https://docs.freebsd.org/en/books/handbook/wayland https://docs.freebsd.org/en/books/handbook/wayland
- giancarlostoro 8mo agoSome people hate wayland.
- AlecSchueler 8mo agoBut surely not every BSD user?
- giancarlostoro 8mo agoNot every BSD user, but the one you're responding to is most likely in that camp.
- AlecSchueler 8mo agoBut then there's no BSD/Linux dichotomy as they suggested.
- pjmlp 8mo agoThose people can contribute to Xorg server further development.
- bee_rider 8mo agoThe thing that kicked off this thread was hope that vim will continue to support X11. No need for continued X development really.
- pjmlp 8mo agoOn the contrary, because you will want to have those drivers when the time comes to reinstall the system with more modern hardware. Without X Server support at the OS level for the new hardware, doesn't really matter if vim supports it on its source code.
- jmclnx 8mo agoNot all *BSDs is FreeBSD :) A NetBSD posted a blog stating NetBSD is having issues porting Wayland due to Linux specific items. OpenBSD stated something similar. Both articles indicated it will be a very long time, if ever, to get Wayland fully working on their systems. I did see this presentation that describes some issues as of 2025. https://www.bsdcan.org/2025/talks/BSDCan2025-jeff_frasca-wayland-presentation.pdf https://www.bsdcan.org/2025/talks/BSDCan2025-jeff_frasca-way...
- hleszek 8mo agoWhy 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.
- NeutralWanted 8mo ago[dead]
- bee_rider 8mo agoWhat is “the Wayland UI,” anyway? Is this like that vim gui program that some Windows users use? Usually vim runs I’m the terminal, so I don’t have any worries about losing support. But other people have other use-cases, of course…
- wpollock 8mo agoThere's always TECO! <Joking>
- jasonhansel 8mo agoI'm glad to see that Vim9 continues to make progress. The center of gravity may have shifted somewhat towards Neovim, but the Neovim ecosystem currently seems targeted towards people who want something more IDE-like. One question is: will more plugin authors move to Vim9Script? It seems that Neovim users have generally moved towards Lua-based plugins, so there's less of a motivation to produce plugins that support both Neovim and Vim9.
- rustyhancock 8mo agoI'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.
- freedomben 8mo ago> That said I'd have preferred something other than Lua if I had the choice. Same. I know we as a community would never agree on what that language should be, but in my dreams it would have been ruby. Even javascript would have been better for me than Lua.
- elros 8mo ago> Even javascript would have been better for me than Lua. Why?
- freedomben 8mo agoBecause I know javascript a lot more than I know Lua (and I suspect given js popularity, a lot of people are in the same boat). Yes Lua is easy to learn, but it's still different enough that there is friction. The differences also aren't just syntactically, it's also libraries/APIs, and more. I also don't have any need/use for Lua beyond neovim, so it's basically having to learn a language specifically for one tool. It's not ideal for me. But the people who did the work wanted Lua, and I have no problem with that. That's their privilege as the people doing the work. I'm still free to fork it and make ruby or js or whatever (Elixir would be awesome!) first-class.
- TristanDaCunha 8mo agoShould stop and help with neovim
- benatkin 8mo agoCould say the same thing about people working on neovim
- logicprog 8mo agoNeoVim has a fundamentally better architecture and healthier ecosystem.
- benatkin 8mo agoBut they're separate highly maintained projects, and there will always be tradeoffs. It's like saying that Ubuntu is better than Debian, or that Fedora is better than RockyLinux.
- aldanor 8mo agoHonestly curious, what are the tradeoffs with vim9 / vimscript?
- jitl 8mo agowell the library ecosystem, developer tooling, and gradual typing support for lua is far ahead of what’s available for vimscript. in my experience lua is #2 behind javascript/typescript’s #1 when it comes to scripting language LSP stuff. both python and ruby suffer from a profusion of alternative type checkers and whatnot that cause pain and fragmentation when it comes to tooling. it’s pretty great to have my vimconfig give red squiggle in editor if i’m doing it wrong before i save & reload. but i’ve not followed vim9 script as its evolved perhaps there’s a good type checker for it at this point? even before neovim, there were vim extensions written in lua so it feels gravity of lua code has been considerable for a long time. to me vim9script feels like perl5/raku split - evolution too late to grow new users, a remnant for a niche that will fade to oblivion slowly over the next 10 years.
- mcswell 8mo ago[flagged]
- mcswell 8mo agoIn 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.
- rfrey 8mo agoIf the thread was deleted by a mod or flagged in the time between starting a comment and hitting "reply", you'd see a message that "you're not allowed to post a comment here" or similar language. Nothing to do with you, it's the state of the thread you're commenting on.
- buzzerbetrayed 8mo agoTake your tinfoil hat off
- hackerbrother 8mo agoHey man, you’re not blocked. Read you loud and clear. Happy Valentine’s Day to you and yours.
- dkga 8mo agoDelighted to see vim continuing.
- computerfriend 8mo agoStrange that there's no v9.2 tag in https://github.com/vim/vim/tags https://github.com/vim/vim/tags.
- c0balt 8mo agoThe relevant release commit is, https://github.com/vim/vim/commit/e7e21018fc0b60c153c8e668f696d95e574cc5a4 https://github.com/vim/vim/commit/e7e21018fc0b60c153c8e668f6... (at time of writing, two hours ago). It seems they didn't publish the tag yet though.
- chrisbra80 8mo agoOopps, missed that. Now there is a v9.2.0 tag and a v9.2.0000 tag
- philipwhiuk 8mo agoI'm curious - what's the logic for both?
- chrisbra80 8mo agoI suppose people not familiar with Vim version numbers may try tag v9.2.0 instead of using v9.2.0000, so for those I added a shortcut
- gilcot 8mo agoMerci.
- actinium226 8mo agoBut where are the AI features?? Gonna get left behind! Only joking of course, actually quite refreshing to see a new version announcement of something this major without any AI nonsense.
- dmd 8mo ago:please exit vim now
- user3939382 8mo agoI 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.
- yojat661 8mo agoThat's pretty nifty. Link please
- jauntywundrkind 8mo agoI used mcp-neovim-server to let my LLM control my vim session. that way it can debug and test and poke around. It's crazy good at debugging plugins. It's absurd how little these things need to look-up docs; half these models are just out the box wildly good at vim. "Open these files on these lines" and now there are four splits with me at the relevant line numbers. Awesome. And it'll explain how to do things & test it out & validate! https://github.com/bigcodegen/mcp-neovim-server https://github.com/bigcodegen/mcp-neovim-server That was a little tricky to set-up. I ended up writing nvim-auto-listen, which uses some heuristics to find your project root, and starts a .nvim.socket in that directory. That makes it easy for mcp-neovim-server instances to find. https://github.com/rektide/nvim-auto-listen/ https://github.com/rektide/nvim-auto-listen/ I'm only somewhat getting started, but the workmanship, fit and finish is just outstanding on Codecompanion, for a fantastically well put together in vim agentic experience. Works really well driving a headless opencode mcp. Being able to stay in vim but still get a great opencode powered experience has been mind blowingly sick. https://github.com/olimorris/codecompanion.nvim https://github.com/olimorris/codecompanion.nvim
- Bulbasaur2015 8mo ago> Vim now adheres to the XDG Base Directory Specification, cool
- srik 8mo ago> For over 30 years, Vim has been "Charityware," supporting children in Kibaale, Uganda. Following the passing of Bram Moolenaar, the ICCF Holland foundation was dissolved […] and its remaining funds were transferred to ensure continued support for the Kibaale project. […] Vim remains Charityware. We encourage users to continue supporting the needy children in Uganda through this new transition. I settled on vim for its technical merits but Bram using his goodwill to fund a charity like this for so long always made me feel good about my choice.
- jdsnape 8mo agoI 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)
- nujabe 8mo agoCurious why you tried to get it approved in the first place if it comes with Linux?
- sobjornstad 8mo agoI worked at a place like this and we had a software registry, where if you had installed something and it wasn't on the registry somebody would start sending you nasty emails. This kind of thing would happen all the time: maybe the Linux machines weren't in the scans, or anything that came with the OS was whitelisted. But if you wanted to install it separately on a computer that didn't have it already, then you'd need to get it “approved.”
- johnisgood 8mo agoEven if it is your own work computer?
- worldsavior 8mo agoYES. Wayland support.
- einpoklum 8mo agoI am a lay user or vim. I use it daily for editing text files and a bit of code, but I always found the plugins and the scripting language rather daunting. There are different, conflicting, plugin management systems; and of course there's the scripting language that's vim-specific, and the few times I tried to delve into this stuff, I quickly found myself in over my head. So - on the occasion of VIm 9.2 coming out - do people have a recommendation for a gentle path to "leveling up" one's VIm skills and engagement?
- svilen_dobrev 8mo agodo 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/_vimrc https://github.com/svilendobrev/svd_bin/blob/master/qini/_vi...
- skydhash 8mo agoThere 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-edition/ https://pragprog.com/titles/dnvim2/practical-vim-second-edit... [1]: https://pragprog.com/titles/modvim/modern-vim/ https://pragprog.com/titles/modvim/modern-vim/ [2]: https://www.oreilly.com/library/view/the-viml-primer/9781680500585/ https://www.oreilly.com/library/view/the-viml-primer/9781680...
- sodapopcan 8mo ago
- k3vinw 8mo ago> The MS-Windows GUI now supports native dark mode for the menu and title bars, along with improved fullscreen support and higher-quality toolbar icons. Congratulations on the new release! Looking forward to applying these awesome improvements.
- _0xdd 8mo agoCouldn't have come at a better time for those who are affected by their IT departments removing access to Notepad++.
- k3vinw 8mo agoThat’s an interesting thought. I don’t believe that Vim’s modal system will be to their taste, but makes me curious if anyone has put together a collection of useful text editing macros for Vim similar to what Notepad++ offers. Typically, I just pipe the output of my buffer to external commands to apply similar transformations that Notepad++ offers out of the box, but I would think the same would be challenging to do on Windows without Cygwin to close the gap. So a Vim macro collection similar to Notepad++ implemented in Vim script or Lua would be pretty cool.
- gilcot 8mo agodo you mean http://cream.sourceforge.net/ http://cream.sourceforge.net/
- gfiorav 8mo agoAs a die-hard vim fan, I feel bitter-sour saying that I switched to nvim. Honestly, I think the vim maintainers should find a way to merge in nvim.
- sodapopcan 8mo agoI 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.
- 3eb7988a1663 8mo agoNeoVim 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.
- kyleee 8mo agoI say we embrace the diversity of both
- e-khadem 8mo agoI 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.
- 8mo ago
- svilen_dobrev 8mo agoi have been using vim since v4 (1999?), but in the last year+ - maybe since v9? - there's some weird defect happening only once in a while: While walking around a file with keyboard, sometimes a random line's indent is removed - that is, text goes left-flushed. AND it's not a tracked change that can be UNDOne - as if it never happened / always has-been-so. Have not been able to correlate this to any other thing. It happens like once a few days, very rarely it might happen twice within minutes. Sometimes i notice that, sometimes i don't and (luckily) python screams of broken indentation. If the file isn't deeply nested python.. good luck. Has anyone "achieved" such a thing?
- simoncrypta 8mo agoAfter many years being interested, I finally invest a good amount of time learning vim properly. Thanks to AI, I got more time to learn in between request and it become painfully slow to use IDE or ask AI simple change. To me the agentic workflow make it even more valuable to learn vim since I can fix and iterate on small details way faster.
- PlatoIsADisease 8mo agoI think with AI, its eliminated my need for Vim. Sorry to say. I was such a proponent. If I'm entirely reading code for bugs, then using voice to text to the AI to correct the problem... What typing am I doing? Still love the idea of Vim.
- deleted 8mo ago[deleted]
- riffraff 8mo agothis is a richer changeset than I would have expected, I'm glad to see that.
- notorandit 8mo agoWayland support for a terminal editor? Woot?
- Biganon 8mo agoMaybe read the very next sentence?
- notorandit 8mo ago> Modern Platform Support: Full support for the Wayland UI and clipboard has been added. On Linux and Unix-like systems, Vim now adheres to the XDG Base Directory Specification, using $HOME/.config/vim for user configuration. Yes.
- wvlia5 8mo agoThere was a time when Bram Moleenar refused to do any updates to Vim, until Neovim came along.
- saila 8mo agoNow that he's no longer with us, I don't think comments like this are necessary.
- wvlia5 8mo agoI just learned that he passed from Wikipedia. I remember he used to get a lot of flak on HN for not wanting to update vim, back in the days.
- quasarj 8mo agoBeing dead has no impact on the truth, actually.
- gilcot 8mo agoAnd that’s not true! He did want to keep the editor stable and available for many platforms and compatible with vi. Rejected proposals break one of these rules.
- saila 8mo agoTrue, but the point could have been made in a more tactful way, and it didn't add anything useful to the discussion anyway.
- laladrik 8mo agoYou know, that new inline Vim's diff algorithm looks really tempting. I wish I had it in my Neovim
- super_mario 8mo agoCongratulations to Christian and all the contributors on another vim milestone. Thank you all. I am so thrilled to see vim development continuing. As early vim (vi imitation) user on Amiga, I can't imagine living without it.
- _0xdd 8mo agoI love this editor. The return on investment in learning vim is incredible. I'm not a programmer or even really "in" tech, but when my colleagues see me chew through a document using MacVim they're astounded.
- wraith_cz 8mo agoI love Vim. I have been using it since the days of DOS and appreciate its amazing compatibility. Since those DOS days, I have been using my vimrc, which I am constantly improving. Today, it is 83 KB and still works, which is fantastic! Over the years, I have tried various other editors and IDEs, including neovim, but nothing beats Vim. Today, I know that I will be with it until I die. It is an amazing piece of software. With version 9.2, it has improved again, and I am delighted with the vertical panel and autocompletion in the search bar. The only thing missing for complete perfection is full-fledged modal dialog boxes.