Is there a .vimrc that already maps all the standard notepad++ keybindings in one go ?

You may find someone who has one, but I just did the ones I found myself missing as I encountered them.

I tried someone’s all-in-one .vimrc, but it broke too many community recipes while rebinding a bunch of shortcuts that weren’t in my muscle memory anyway.

I kept adjusting my .vimrc as my muscle memory transitioned. So having less to fiddle also made it easier for me to keep my .vimrc tuned to my muscle memory.

For example, I was using / instead of Ctrl+F because I liked it better within a month or two.

what’s good about neovim?

• NeoVim supports plugins written in modern languages without a Vim script shim. Vim script is utterly awful, and the sooner we can all pretend it never happened, the better the world will be.
• NeoVim can be configured and extended with lua a language that many people actually like to use.
• NeoVim is built client/server style, like VSCodium, so it can do the same remote/local mix and match tricks. Notably, VSCodium works nicely as a front end for editing files with NeoVim.
• NeoVim is somehow actually faster. vim was no slouch, but a full rewrite seems to have added some…ahem…vim.

I just drag my vi terminals to another workspace and launch a new editor.

I see what you did there. Lol.

Yeah. And VsCodium with NeoVim is fantastic.

But if ctrl+f doesn’t let me type a search term then I’m going to scream

It’s been awhile since I’ve bothered to remap a key in Vim, but adding this to .vimrc should do it for you:

nnoremap <C-f> /

I started with a bunch of these to let me keep using existing muscle memory while training new.

Yeah. After that everything can be done with !sh.

(Edit: This is a joke. There’s a lot of reasons not to do this.)

I think I get what you are intending to imply by the word “intuitively”; it’s that it eventually becomes as reflexive and fluid as touch-typing itself.

Exactly like that!

It’s also another source of the many “I can’t exit Vim” jokes, because it is now genuinely disorienting for me to try to edit text without Vim key bindings.

Gosh you make it sound almost like you play Vim like an instrument more than use it…!

That’s a great analogy. It does very much feel that way.

Honestly that sounds cool ^_

It is pretty cool.

Wether it’s really worth the learning curve is probably unique to each person that tries it. But for folks who need to edit a lot of text a lot of the time, it’s pretty great.

It’s intuitive if your previous editor was ed(1) and you’re using an ADM-3A-like keyboard.

Exactly! Ha!

Nice.

I’ve been using Vim daily for about 20 years, it saves me 30 minutes at a time regularly.

I’m approaching break-even on the learning curve!

I’m kidding…mostly.

Doesn’t matter we will tell you either way.

• Instead of simply shortcuts, vim uses “chords”. Every new shortcut I learn can be combined intuitively* with all the other shortcuts I know.
• Because of this there’s no faster way to edit files than Vim in the hands of an experienced user.
• this let’s me spend almost no time editing code, freeing up the rest of my time for swearing at piss poor documentation.

* I use “intuitively” here in a way that not merely stretches, but outright abuses the definition of the word.

Yeah. I don’t mind snap at all for cases where a better package doesn’t exist.

What made me give up Ubuntu was how it railroaded me into snap versions of packages that work better, for me, as native .deb installs.

the thing people dislike about that is that you’re silently moved from an open system to a closed-source one.

Yeah. I didn’t realize I had fallen for it until I tried to automate a system rebuild, and discovered that a bunch of the snap back end seems to be closed and proprietary.

And a lot of it for no reason. Reasonable apt and flatpak alternates existed, but Canonical steered me to their closed repackaged versions.

FUCK IT, I BUILD FROM SOURCE CODE FROM SHADY GITHUB REPO_*

I feel seen.

Lol. It’s not the groundhog we should be watching, then?

They probably mean Open Container Initiative (OCI), the protocol shared by Podman and Docker.

Yeah. The idea of an automated C to Rust replacement of the Linux kernel is fascinating. As you say, there’s probably stuff in the Kernel that Rust’s compiler won’t allow.

I imagine it wouldn’t work at all, out of the box, but it might reduce the cost curve enough to make a dedicated team of very clever engineers able to cross the last mile, given time.

As cynical as I am of both Rust and AI generated code, it honestly feels like trying an automated conversion might be less of a long shot than expecting the existing Linux kernel developers to switch to Rust.

And I’m sure a few would kick in some thought cycles if a promising Kernel clone could be generated. These are certainly interesting times.

Lol. If Rust fans want a Rust kernel, no one is stopping them from building one.

and therefore is the one and only acceptable proprietary launcher.

Yep! But that’s only until they decide to enshitify, which they (Valve) will, because they (the humans making the correct choices today) will sell or retire.

Makes sense. I only really replied there to help anyone reading along.

There’s many very basic features of vim that VsVim does not have (like… almost all command line commands), basic features which regular vim users use all the time.

! is supported:

https://github.com/VsVim/VsVim/blob/master/Documentation/Supported Features.md

It sounds like you haven’t tried VsVim in a long be time, or had an unusually bad experience with it.

(Edit: My responses to your other points were my old man energy, and not worth anyone’s time, so I removed them.)