I get stressed out every time I need to jump into a server and check something and the only editor is vi. If I can I install nano straight away. Btw, :q! does nothing without pressing ESC first! Hehehe

I'm feeling old now... I've been using vi for 35y now and was happy when I got vi.exe on a dos box, as I hated edit. I still don't like 'simple' editors like nano/joe.

I used kill to get out of emacs when trying it agter 7y of vi usage, so I get the need to get mideval on editors users aren't used off. ;)

Insert Mode tho

Nano's only appeal is that it's beginner-friendly, but you already know Vim, so why switch?

Micro exists. It's Nano with Lua plugins. Very robust and minimalist. No magic incantations. I actually use it to code simple stuff that I just don't want to wait a minute for VSCode to spin its wheels.

WTF. Why? I could maybe see someone preferring emacs over vim, but not nano. Maybe there are nano features I don't know about, but it just seems like Windows Notepad to me.

I normally just use VS Code with a VIM extension. Unless I'm ssh-ing into something, then I use vim.

"vim" isn't a valid PID. I think you meant killall -9 vim

My main problem with vim is that they use hjkl instead of jkl; , it doesn't make sense to me why they'd do that.

With qwerty you can be sure of layout of the letters and numbers across languages.

Been a vim user for decades but never used hjkl. Probably strongly correlated with the fact I'm non QWERTY as well (Dvorak). I just use the arrow keys combined with the jumps to start/end of lines/words or to characters.

You don't need to remap anything aside from hjkl as the keybindings are mostly mnemonic and not location based.

On Dvorak at least, ^C is so easy to press that it's great for switching modes, I never use Esc.

I find the more time you've spent in non-graphical shells, especially on low spec devices or laggy connections, the more you appreciate vim. Instead of pressing Del a bunch of times and having it overrun you can ct" to swap out that string. I even use vim keys in vscode, as my hands are so used to them.

My biggest complaint is logging into some legacy device that only has vi and not vim, when shortcuts like "dap" or "caw" don't work

Remember to actually kill the process though, since that will only background/suspend it in most cases.

(Be sure to save the file though first, Vim creates a "swap" / recovery file but its best to not rely on that, use fg to re-open, then press escape and type :wq)

Followed by kill -9 %1 to actually kill the process, otherwise your terminal might complain or freeze up when you try to close it