Vim as Language
benmccormick.org
benmccormick.org
I find dired, tramp, org-mode, auctex, magit and good async support indispensible and the Vim equivalents are either less powerful or non-existent.
For moving beyond the basics I suggest this book: http://pragprog.com/book/dnvim/practical-vim
For vimtutor it's introduced in the first part http://benmccormick.org/2014/06/30/learning-vim-in-2014-the-...
The most disturbing thing when learning vim is the fact that shortcuts actually "means" something rather than being near your fingers. Like the old flashioned way to use shortcuts in RTS games vs grid modes.
"Your problem with Vim is that you don't grok vi."
http://stackoverflow.com/questions/1218390/what-is-your-most...
An example of vi/vim's power I've used for ages is formatting a paragraph of text: {!}fmt<cr>
With text objects, in the middle of a paragraph somewhere,!pfmt<cr> -- Much easier to type!
(yes, I know vim has the gq command, but I prefer piping text to the *nix fmt command.)
Vim, "a great editor, utterly lacking a decent window manager"
The latter is just outright painful -- tabs, windows, and buffers, so much promise, yet...such fail O_o
by context switching to the grey matter to inquire what the name of the file is and then tab complete your way to said file vs. where you visually "know" the file to be in standard panels (splits) with tabs (buffers) based editors.
> move a file between different windows
please don't lie to the uninformed -- one can only rotate windows within the same row or column, not across columns and rows -- it's rather limited.
> create and destroy splits, etc. is just so nice
I'd take drag and drop splits any day over Vim's adhoc implementation. If you create a split it's best to destroy it as it will never behave predictably; i.e. your split layout may completely collapse when closing a buffer.
and then cloned splits, man do I love to see the exact same file displayed across splits, nothing says maximize screen real estate usage like cloned content. Sure, can close the cloned split, but why waste one's time on an event that isn't even possible in GUI editors? (i.e. attempting to open an already open file brings you to its location, not pointlessly duplicates it).
> Every other editor seems clunky and inefficient
Feel the same way about Vim's window management, try Sublime, heck even try Eclipse, you get multiple visible tabs (buffers) per panel (split), and as an added bonus, the labels are set above the code (where top-down, left-right humans expect it), not below. You can also quickly hotkey rotate through all opened files, bing, bing, bang vs. either reading through a buffer list that has nothing to do with its location in visual space, or praying that ctrl-O doesn't start opening files from a previous session, or just saying ctrl-6 (toggling between 2 measly files) is the answer.
I think the deal with Vim is that you have to keep a lot in mind, literally, as in the entire set of file names you're working with, vs. visual editors where code location is representation (i.e. its "name").
What language is that? Oh, I see, thats "customers please go away" written in techie-language.
Well, I didn't learn a lot about Vim from that, but I know not to go back. Too bad, I like Vim.
I use them to manage caching and anti-DDOS for my site. Most people don't see that message, not sure what would have set it off for you. It's not a site specific feature, just a byproduct of using cloudflare.
I'll take a look when I'm off work later.
[1]: https://support.cloudflare.com/hc/en-us/articles/200170096-H...