The rootwork v0.2 blog posted about the author's journey through text editors, from classics such as vi(m) and Emacs to tools I've never heard of. They explain what they use the editors for and why.
At work I have to do a lot of development in an on browser based IDE, which means no nice #emacs movement shortcuts like I'm used to, and moving around the code is painfully slow. The IDE does support #vi movements though, which I've been trying as a 'better than nothing' solution, and yeah, it's still hard. I don't think I'll ever get used to the logic of: if "h" is left/back, then "j" is down, and not up. Arghhh.
The #hacker/detective in #MurderAtTheEndOfTheWorld tested to see if another person was a hacker by asking them if they preferred #emacs or #vi. Apparently any hacker would have an uncontrollable reaction to that question.
VIM is great in many ways but why is the default behavior of "paste" to overwrite the register? This seems like a huge problem that I'm always fighting, every... single... day...
Is there some ancient reason why this was a great default behavior? #vi#vim
I’m wondering how many people writing programs on #zos under #uss (Unix System Services) using C and #curses library? If you are looking for smell of real Unix development, try to compile here using make (not GNU) pure #vi and sh near to true Born shell (no, it is not #ksh). Anyway curses based menu to present selection list feeding data from stdin is usable from now.
#vi & #vim real deal: most of you use “:wq” when you should be using “:x” instead. Not only does it only change the timestamp on change but one less character.