gvim is easier than vim and vim is easier than vi; with gvim, you can use the mouse, unlike console versions. In general, using *vi is most valuable for editing, as opposed to entry—things like reformatting code, adjusting text tables, that sort of thing.
You only need a small set of commands to function in gvim—i/esc for modes, v for visual (selection mode), d, y and p for cut, yank (aka copy) and paste. You can skip the home-row cursor motion stuff at first and just use arrows. Once you’re comfortable with a small set of commands, learn a few more at a time, spaced out, and when you have a particular need for them. Start with ‘.’ (repeat last command), since having that while doing semi-redundant editing tasks will motivate you to learn more commands.
gvim is easier than vim and vim is easier than vi; with gvim, you can use the mouse, unlike console versions. In general, using *vi is most valuable for editing, as opposed to entry—things like reformatting code, adjusting text tables, that sort of thing.
You only need a small set of commands to function in gvim—i/esc for modes, v for visual (selection mode), d, y and p for cut, yank (aka copy) and paste. You can skip the home-row cursor motion stuff at first and just use arrows. Once you’re comfortable with a small set of commands, learn a few more at a time, spaced out, and when you have a particular need for them. Start with ‘.’ (repeat last command), since having that while doing semi-redundant editing tasks will motivate you to learn more commands.