You don't ever close vim. You pray to the gods and hope that vim chooses to quit for you. (technically accurate if you think about it - i.e. otherwise you leave swap files all over the place:-P)

And hope that you do not mess up and summon a daemon instead:-P.

One of the interesting aspects of humanity is how much people like given text editing methods. There's a handful of approaches and after learning one or two, people really figure out what works for them.

I am more than happy to say I like vim, but in the end you should use what you like best. Just done be surprised when I can write and edit a ton of text really fast while your nano session is comfortable, but slow.

I will and I will exit nano easily

What does it carry over from your swim config? What are the benefits of using Nvidia inside of VSCode as opposed to just nvim?

This was the thing that stopped me from hopping over in the first place, the vim binds just make too much sense

My comment really applies more to vi than vim but everyone’s using them interchangeably nowadays. When implementing systems where internet connection or excess install size aren’t possible or recommended, you gotta be able to work with the tools at hand.

Of course, the comparison is custom cabinetry to ikea. Your local meth head needs to understand how to use hand tools because he or she may need to use them for myriad reasons ranging from “I don’t have the power version of this” to “it’s faster” to “the cut is cleaner” to “they pay me more to use this”. The person designing hudfł needs to be concerned first and foremost with how to shave a sixteenth off every panel so his accounting department doesn’t have to pay to reforest an extra hundred acres this year.

Perhaps someone working entirely in programming has good reason to not know vim, but I still cling to the antiquated notion that the person designing furniture out of manufactured materials ought to be able to build a box you’d feel comfortable with company seeing.

But I must be stopped!