71–80 of 409 posts
Here are some tips:
Try to limit yourself to one vim session per day, then one session per week, and so on.
Try to replace some Vim sessions with Emacs.
Buy notebook with keyboard without Esc key.
Install an OS without Vim.
Use mouse.
Earlier quoted context omitted.
I live in a different universe to you it seems. The only vim command I know is :q . Honestly, I tried several times over the decades and walked away with my head buzzing. PS: I don't live in emacs either! What I do love in both camps is how the explanations begin... "All you have to do is...[insert irrational (to non-vim/emacs users) command]" which makes me laugh every time. Love the article, which ironically proves…
I know some basic commands and know it well enough to edit git commit messages and interactive rebase (`ddkP` is probably the most advanced command I know). But I've never thought "I prefer this over my regular editor this is amazing". I just don't get the satisfaction. And of course I'd have to dive deep into the ecosystem in order to get the same benefits that my main editor provides out of the box, like idk, cmd+c…
From the readme: "Remotely: $ while true; do curl http://vi-host:8888/kill-vi-$RANDOM; done vi will eventually exit" Bold claim, and how would you know? What if there is a network partition preventing you from getting the message that exiting vi failed and Chuck Norris?
Almost as important a problem in Computer Science as P!=:WQ.
The best advice I ever received was, you next open emacs and leave the session running the rest of your life.
I think the more interesting question is, after you eventually exit vim, what do you do next? The best advice I ever received was, you next open emacs and leave the session running the rest of your life.
The question is not "How" but "Why" you would want to ever do that in the first place;-) Many years ago I knew a university professor and students said about him he might leave uni occasionally but he sure never leaves Emacs. Some live in Emacs, some live in Vim.
I honestly don't know how vim deals with unsaved changes upon shutdown and don't use it enough to look that up, so that's why I'll first exit. As to why shutdown: cultural thing in the end. I was raised with the idea that wasting is bad (and objectively speaking it's very hard to argue with that) so if I don't need the machine running after I'm done with it, I just can't stand the idea of the thing using energy liter…
You can also just suspend it (ctrl+Z), and resume it with fg.