I first tried vi in the early 90s, before I had easy access to online resources. I had to open a new shell and kill the vi process to exit it. Next time I dialed into my usual BBS I asked how to exit that thing. But since then I’ve liked it, because vi has been on every system I ever ssh’ed into.
You quit it just like you quit ed or ex, just that you have to enter the prompt (:) yourself as vi is not by default in prompt mode. And you should know ed, ed is the standard editor.
I can exit Vim, it just feels like trying to rip out the dashboard and the interiors from a family car because race cars also lack them. Kate is a good speedy alternative to VSCode, not to mention it also does not have Microsoft’s greedy hands on it.
Out of the box, Vim’s default configuration is very basic as it’s trying to emulate vi as close as possible. It like if you want things like headlights or a heater or a tachometer in your family car, you got to create a vimrc and turn those features on. That was my experience when I first started using Vim - I spent a lot of time messing around creating a vimrc until I got things the way I wanted.
One of the big changes with Neovim is their default settings are a lot more like what you would expect in a modern text editor.
I wanted to follow up with the other error, where you didn’t open a file, so it doesn’t know where to write, but :q! always works :/
Can I somehow not discard my changes tho? I always open a 2nd terminal in root only for vim when editing system files so I don’t have to re-do the whole config but this time in sudo.
Ah yes, the legendary filter
I first tried vi in the early 90s, before I had easy access to online resources. I had to open a new shell and kill the vi process to exit it. Next time I dialed into my usual BBS I asked how to exit that thing. But since then I’ve liked it, because vi has been on every system I ever ssh’ed into.
You quit it just like you quit
edorex, just that you have to enter the prompt (:) yourself asviis not by default in prompt mode. And you should knowed,edis the standard editor.I use Helix btw.
I can exit Vim, it just feels like trying to rip out the dashboard and the interiors from a family car because race cars also lack them. Kate is a good speedy alternative to VSCode, not to mention it also does not have Microsoft’s greedy hands on it.
I don’t get your analogy, but (neo)vim is a full featured IDE if you configure it to be one
Out of the box, Vim’s default configuration is very basic as it’s trying to emulate vi as close as possible. It like if you want things like headlights or a heater or a tachometer in your family car, you got to create a vimrc and turn those features on. That was my experience when I first started using Vim - I spent a lot of time messing around creating a vimrc until I got things the way I wanted.
One of the big changes with Neovim is their default settings are a lot more like what you would expect in a modern text editor.
Yeah that’s a fair way to look at it
:x
it says I don’t have permission
:q!
I wanted to follow up with the other error, where you didn’t open a file, so it doesn’t know where to write, but :q! always works :/
Can I somehow not discard my changes tho? I always open a 2nd terminal in root only for vim when editing system files so I don’t have to re-do the whole config but this time in sudo.