3 ms·
Oh wow, he really changed his pricing model. It used to be a $10/mo subscription w/ access to all videos. Sorry about that! > maybe it'll push me over the edge
by benjamincburns 13y ago
Oh wow, he really changed his pricing model. It used to be a $10/mo subscription w/ access to all videos. Sorry about that!
> maybe it'll push me over the edge to do the right thing
Oh, there's no "right thing" here, there's just efficient and inefficient. Don't let some asshole like me tell you "you're doing it wrong!"
I hear you on the frustrating process breakdown during the learning curve. However, if you want to learn it I promise that it's much quicker to go the painful route and just dive in. Start off with just the basics, then every time something feels repetitive, go look it up. When you go to look something up, start with the internal help system, then move on to Google. Do ":help help" to learn how to use the help system.
For me it took about a day before I wasn't stopping every 5-10 minutes to look something up, a week before I wasn't stopping every hour, and I still run into stuff every couple of days where I say to myself "okay, this is too repetitive, what's the magic vim way?"
Something that also helped me - if you want to be fast, remember that the slowest thing you can do is read. So in terms of movements, it's bad to just keep tapping 'j/k' until you see what you want. That's like the O(n) approach. Then there's search with an incomplete key. That's like O(logN). But then there's search with a good key that you know will hit what you want first try - that's O(1). Then there's the command-t plugin and/or the :vim command...
Also, either get used to using ctrl-c instead of ESC, or remap your capslock key to ESC. I prefer the latter. Not sure how to do it on Windows, but on Linux see xmodmap, and on OS X see PCKeyboardHack.
Syntax highlighting/indenting: add the following to ~/.vimrc
filetype on
filetype plugin on
filetype indent on
syntax on
Tabs - see :help tabpage.txt, though I prefer windows (see below).
Completion's a bit weird in vim, but for starters there's always ctrl-n/ctrl-p in edit mode. For more advanced stuff, see Omni completion: http://vim.wikia.com/wiki/VimTip1591 http://vim.wikia.com/wiki/VimTip1591
For side-by-side split views, check out :help windows. Ctrl-w, n creates a new horizontally-split window; Ctrl-w, v creates a new vertically split window; Ctrl-w, c closes the current window; Ctrl-w, j/k/h/l switches to the next window up/down/left/right; Ctrl-w, J/K/H/L moves window to the extreme.
As a cheat, I've got the following in my .vimrc for nice split screen (window) buffers that automagically resize based on which one is currently in focus (taken from destroy all software):
set winwidth=84
" We have to have a winheight bigger than we want to set winminheight. But if
" we set winheight to be huge before winminheight, the winminheight set will
" fail.
set winheight=5
set winminheight=5
set winheight=999
Wow, okay... this is a lot longer than I initially intended. Anyway, good luck!