Live data from Hacker News

Vim 9.2

vim.org

181–190 of 203 posts

Re: Vim 9.2

#181

Earlier quoted context omitted.

Big companies can be incredibly penny wise and pound foolish because their beancounters make them obsess over the wrong metrics. My current company has spent the last year cost cutting every single way to stay afloat and now you need a chain of approvals up the management ladder with detailed explanation for every paperclip you want purchase. I can't prove it, but I am willing to bet my entire salary that the costs o…

And they're probably feeling the need to pinch because they are moving slow and falling out of relevance. When you're being outcompeted and outmaneuvered it's important to slow down and make sure you save a few dollars wherever possible, apparently.

You write "wherever possible", but: Have you ever seen the beancounting itself having been under scrutiny?

I'd wager a big part of it is also the same politics based asymmetry that's visible everywhere; like nobody ever got fired for buying IBM or people only get credit for managing a crisis, not preventing it in the first place.

Re: Vim 9.2

#182

But 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.

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?

Does it count if I share my experience with AI and nvim? I use it to update my configuration, discover new plugins, write custom lua code (I don't know lua) and inquire about motions that would help me in specific workflows. I started learning vim motions last summer and AI really lowered the entry barrier and allowed me to focus on the motions rather than the setup.

Also related to my nvim workflow but not strictly vim related: I use AI to write and update a bash script that handles tmux windows. Again, it lowered the barrier to entry and it made switching to nvim as my primary editor easier.

Re: Vim 9.2

#183
post #63

Earlier quoted context omitted.

How many people don’t know tmux in the industry is really beyond me.

With all the buzz about orchestrating in the age of CLI agents there doesn't seem to be much talk about vim + tmux with send-keys (a blessing). You can run as many windows and panes doing so many different things across multiple projects.

The way I see it using tmux to orchestrate multiple agents is an intermediate step until we get a UI that can be a product offering. Assuming we get orchestration to the level it has been touted, there is a world where tmux is unnecessary for the user. You would just type something to one panel in which the "overlord" agent is running (the "mayor" if we talking gas town lingo) and that agent will handle all the rest. I doubt jumping between panes is going to stick around as the product offering evolves.

Re: Vim 9.2

#184
post #106
post #67

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

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

That’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.

Re: Vim 9.2

#186
post #111

Earlier quoted context omitted.

What do you mean? Neovim looks 100% exactly like Vim when you turn it on without any plugins. It's hard to distinguish even. It's the plugins that give it that nerdy look.

they probably mean GUI app like GVim and MacVim

I personally wish they'd resurrect elvis

Re: Vim 9.2

#187
I 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.

Re: Vim 9.2

#188

i 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 h…

I'd bet it's some plugin. I have a vanilla Vim and never noticed anything like that.

Re: Vim 9.2

#189

Earlier quoted context omitted.

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

Lua, especially with LuaJIT, is nearly as fast as C. I certainly don't want to have to run a slow language like Ruby or especially a full blown JS runtime like V8 just to run Vim, the entire point is speed and keyboard ergonomics, otherwise just use VSCode.

  >  a full blown JS runtime
I absolutely hate all the random things that install npm on my machines

Re: Vim 9.2

#190
post #102

Earlier quoted context omitted.

Curious why you tried to get it approved in the first place if it comes with Linux?

I 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 nee…

  > maybe the Linux machines weren't in the scans
Honest question, how would you actually detect this? I mean I understand using the package manager install (and that's easy for them to control) but building from source and doing a local install (i.e. no `sudo make install`)? Everything is a file. How would you differentiate without massive amounts of false positives?
Post reply on HN