Earlier quoted context omitted.
I think we just don't agree about what the good parts of vim are. I find f and t to be a minute improvement over forward search. I think hjkl is strictly better than arrow keys, because you don't have to move your fingers from the home row to navigate a file, and I think the basic editing commands I outlined are sufficient for a superior editing experience within a day of learning them, no deep study required.
i'm sure it becomes intuitive with lots of use, bit i find it awkward with having to move my finger off the home keys to move left. somehow for me, its even more confusing that way. where as my arrow keys are completely intuitive, one finger for the left and right keys and the middle finger handles up down. to me its not a big deal to remove my fingers from the home row if i already have to move from the home keys.
Interactive Vim tutorial
151–160 of 230 posts
Re: Interactive Vim tutorial
#152It's using hardcore classic vim key bindings. Insert mode doesn't even start when pressing actual Ins. I understand some can have nostalgia for the times of archaic terminals, but I find it counter productive. Sorry, but I'm going to use Ins and regular arrow keys, not i and h,j,k,l.
Re: Interactive Vim tutorial
#153I've tried learning Vim several times, but the need to switch modes and back for cursor movement has been a huge turnoff, especially considering the location of the ESC key. It seems to just conflict with the way that I type, where I am frequently jumping my cursor around in the middle of text editing, which is effortless in Emacs. Maybe mastering Vim is not just about memorizing key combos but about changing your co…
> especially considering the location of the ESC key This can be solved by remapping ESC to Capslock.
Re: Interactive Vim tutorial
#154My biggest vim efficiency booster is remapping to "jk"
What do you do when you actually need to type the string "jk"? Type "j", then wait for sometime and then type "k"?
Re: Interactive Vim tutorial
#155Alternatively, don't try to hurry enlightenment. First, learn :q! Next h,j,k,l Then i and ESC Finally :w Now you know vim. Don't let people tell you you're using too many keystrokes. Are you still reaching for the mouse? If not, you're using vim just fine. Most of the good stuff in vim, you'll learn accidentally, because you're in normal mode when you think you're in insert mode, or because you have caps lock on in n…
I think i and Ctrl+[ is better? It's more in line with the idea of keeping your hands near home row.
Re: Interactive Vim tutorial
#156Earlier quoted context omitted.
Sorry, but I think that's really bad advice. For one thing, it doesn't give new users any positive experience or reason to learn vim. If all you learn is to do things that are "pointless" (like learning hjkl), then you won't get any value out of vim. And if your way of learning is to do something that screws up your file and try to recreate how that happened, well, let's just say that every time I do something that s…
I think we just don't agree about what the good parts of vim are. I find f and t to be a minute improvement over forward search. I think hjkl is strictly better than arrow keys, because you don't have to move your fingers from the home row to navigate a file, and I think the basic editing commands I outlined are sufficient for a superior editing experience within a day of learning them, no deep study required.
I just feel like it's a thing that people don't realize will help until they internalize it. Whereas almost everyone I show the text objects to immediately realizes their utility. I'm only looking at this from a pedagogical perspective.
Re: Interactive Vim tutorial
#157Alternatively, don't try to hurry enlightenment. First, learn :q! Next h,j,k,l Then i and ESC Finally :w Now you know vim. Don't let people tell you you're using too many keystrokes. Are you still reaching for the mouse? If not, you're using vim just fine. Most of the good stuff in vim, you'll learn accidentally, because you're in normal mode when you think you're in insert mode, or because you have caps lock on in n…
> i and ESC I think i and Ctrl+[ is better? It's more in line with the idea of keeping your hands near home row.
Re: Interactive Vim tutorial
#158Earlier quoted context omitted.
Sorry, but I think that's really bad advice. For one thing, it doesn't give new users any positive experience or reason to learn vim. If all you learn is to do things that are "pointless" (like learning hjkl), then you won't get any value out of vim. And if your way of learning is to do something that screws up your file and try to recreate how that happened, well, let's just say that every time I do something that s…
I have been using Vim for 15 years now and I completely agree with sevensor's comment. - Vim is not newbie-friendly regardless of whether you remove guioptions or not. One has to spend at least a few hours of study and practice to get comfortable with Vim. If one is forced to invest a few hours to learn an editor, one might as well get rid of guioptions and follow other advice provided in sevensor's comment. - Learni…
On the other hand, if I want to show someone the "good parts" of vim, I try to show them something they can't do in another editor, rather than something that they can do (arrow keys). Even if I 100% agree that arrow keys are a worse experience, it's just not as convincing as something that can't be done outside of vim.
At least in my experience.
Re: Interactive Vim tutorial
#159It's using hardcore classic vim key bindings. Insert mode doesn't even start when pressing actual Ins. I understand some can have nostalgia for the times of archaic terminals, but I find it counter productive. Sorry, but I'm going to use Ins and regular arrow keys, not i and h,j,k,l.
Then you’re missing the point of touch typing the commands from the home row.
Re: Interactive Vim tutorial
#160My biggest vim efficiency booster is remapping to "jk"
What do you do when you actually need to type the string "jk"? Type "j", then wait for sometime and then type "k"?