What developers really mean
View 11 previous comments
38w
Seen this many times over many years, still valid!38w- 38w
^X^Cquit^\[ESC][ESC]^C38w
Vi makes sense when you realise that editing is different to saving/loading/searching etc, which are commands. You should not really mix the two. I like latex for writing documents for this reason. It separates content from typesetting. When you put everything in the same bucket (like with WYSIWYG), you make it quicker to do things, but only because the editor is doing more things for you that you are unaware of. Eventually this bites you on the arse.37w
37w
+Jason Thorne You're absolutely correct.
Vi is a great editor for writing Bash or AWK scripts, config files, plain text and small-ish python programs, but isn't appropriate for stuff that needs advanced features like you'd find in M$ Word or LibreOffice.
On the flip side, those tools totally suck if you want to write programs. I tend to use Komodo IDE for most larger programming jobs.
I also use vi mode for the bash shell. Being able to search the command stack and do vi editing is a huge benefit.
Now we need to get everyone into a ksh/bash/zsh/tcsh holy war. :D37w
