[…] Why Vim? […]

[…] vim. It does require some getting used to and some configuration, but it is absolutely worth it. * Why vim? * Vim for beginners * Learn vim […]

[…] Git interactive rebase requires you to know it, and if you’re still not convinced, maybe this great article will make you change your […]

[…] http://www.terminally-incoherent.com/blog/2012/03/21/why-vim/ […]

[…] besides, it’s difficult to say which one of these editors is better than the other. It really depends on who you ask. I don’t have a good answer to this so I’ll opt-out and provide […]

If anyone needs to go out of their way to try to explain why they’re using something as trivial as a text editor — and backing up his explanation with niche, biased examples such as “Suddenly you realize you want to copy the current line and paste it directly below the first. How do you do this?” (and that is very intuitively achievable in Netbeans that I don’t even think is excellent, but I digress) — then this is the very symptom that the software in question, Vim, is not worth the trouble. The sure trouble.

Enjoyed the article but it did not take literal seconds to register a single keystroke at 300 baud. Given 8 bit ASCII you can do 18 round trips per second.

Very useful. Thanks :)
———————
Bardzo ciekawa strona + fajnie widzieć dobry tech-blog pisany przez “swojego” :)
Pozdrawiam

Adam

@ juliob_m:

Julio, ya que eres Español, te contesto en español. Probablemente, no hay razón por la cual no puedas usar LibreOffice (u OpenOffice).

La funcionalidad está y es muy buena. Soporta tanto los estandares abiertos odt como los de MS (.doc, docx, etc), a veces mejor, que las diferentes versiones de MS. Es rápido, intuitivo y trabaja bien con archivos muy grandes.

tl,dr translation: Libre/OpenOffice work just as well, it’s sometimes more compatible unlike different MS Office versions and it’s fast. Probably no reason not to use it.

Two comments. First, as someone else pointed out, using a substitution command is a lot easier than using a macro in that little example you gave. I understand that you were trying to explain macros, but one command is a lot quicker and easier than going through all the trouble of creating a macro.

The other thing I’d say is that the learning curve shown for vi is a bit misleading. I agree about the extremely steep initial learning curve, but to show it flatten completely is to discount the complexity of vi. I’ve been using vi since the early or mid-eighties (when we received Berkeley Unix 2.9 for PDPs), and while I’m pretty good at it, every one in a while I still see a new trick. Actually, I think I’d say for regular expression usage alone, that flat line needs to continue up a bit, as most people never really master regular expressions.

Finally, and it’s perhaps been too long for me to make a real assessment of this, but usage was at least loosely based on ‘ed’. The ‘y’ command was there, as were regular expressions, substitutions, etc. Not as fully functional as in vi, but if you had been using ‘ed’, as I was at the time, ‘vi’ was different, yet recognizable as being related to ‘ed’.