6 ms·

Before trying these courses , Please try vimtutor that comes bundled with vim . After practicing with vimtutor , you can try these additional courses.

mhaberl 6y ago
For anyone wondering, you use it by executing vimtutor in terminal (not in vim). Also, you exit by pressing ESC and then typing :q (hit enter)
- libria 6y ago
  How fitting that the tutorial for vim needs its own pre-tutorial for exiting.
  - Izkata 6y ago
    It's also in the tutor, lesson 1.2 But there's actually nothing special about vimtutor here: all it does is write a temporary file and then open it in vim.
  - samstave 6y ago
    Before replying to your post I upvoted, I had to hit a link called [REPLY]
  - alfiedotwtf 6y ago
    Having seen machines that have hundreds of Vim sessions opened because “system integrators” didn’t know how to exit Vim, it should be the very first thing taught
    - johannes1234321 6y ago
      Luckily vim finally got a bit better with that: on a Ctrl-C newer versions now show instructions for quitting. I remember my first vi sessions (typically via something like `crontab -e` where it wasn't clear to me it picked my "default" editor ... thus didn't know where to read up on it ...) some long time ago, where i knew `kill` before the right command ...
CoffeePython 6y ago
Yep I’d definitely recommend the same, vimtutor is great.
kkoncevicius 6y ago
first vimtutor and then :help user-manual
- gbrown_ 6y ago
  Yes! Sadly a lot of people skip over this despite vimtutor pointing to it at the end. Copy/paste below as the text doesn't need paraphrasing, but also because a lot of comments here seem to be advocating vimtutor as something more than the "brief overview" it is. This concludes the Vim Tutor. It was intended to give a brief overview of the Vim editor, just enough to allow you to use the editor fairly easily. It is far from complete as Vim has many many more commands. Read the user manual next: ":help user-manual".
- 40four 6y ago
  The vim help files are fantastic. Well written, and clearly explain any feature you need to understand better.
rjvir 6y ago
Looks like "vimtutor" is primarily text explaining the hotkeys. For me, the bottleneck to picking up vim has not been merely knowing the hotkeys, but more internalizing the commands and building muscle memory. The interactive game format of this website could possibly solve that, so it appeals to me.
- pksebben 6y ago
  vimtutor is designed for you to use it regularly to train muscle memory
  - D2187645 6y ago
    Vimtutor is free so you are the product.
    - Maha-pudma 6y ago
      So is Vim
- baconsteakey 6y ago
  It says this in the 3rd or 4th paragraph: > It is important to remember that this tutor is set up to teach by use. That means that you need to execute the commands to learn them properly. If you only read the text, you will forget the commands! And it's free, not 15 USD or whatever this site is charging.
  - ketzo 6y ago
    Okay... but the difference between a piece of text just telling me to use the commands so I remember them versus an interactive trainer that provides a structured setting for me to use them is pretty significant, no?
    - boogies 6y ago
      > a structured setting for me to use them is provided by vimtutor. I wish people would take a couple hundred milliseconds to research things like this before posting about them — most [GNU’s Not] Unix commands take less time to run than a webpage takes to load, and installing their packages takes no more typing than a web search.
scottmcdot 6y ago
vimtutor might be a little too intimidating compared to a vim course in a browser.
ajfjrbfbf 6y ago
I started with vimtutor, then installed IdeaVim in all my Jetbrains IDEs, it took me about a week to reach the same level of efficiency I had before. I don't understand how some people can say the learning curve is too steep. Sure it's a bit annoying at first, but it quickly becomes natural, and you don't have to use all features at first. It has allowed me to improve my touch typing a lot. Learning a programming language is a lot more work but hardly anyone ever complain about it. It's been maybe two months and I wouldn't think of using anything else than vim for serious code editing.
- sverhagen 6y ago
  > I don't understand how some people can say the learning curve is too steep I am doing fine with vim for basic editing tasks and use it a lot (mostly when I'm already in the command line). But there's just only so many shortcuts I'm capable of memorizing. This is not a problem for me exclusive to vim, of course. In IntelliJ I also sometimes find an amazing new function that I then don't keep using since I've already exhausted my limited "inclination" of learning new shortcuts. Also, I don't think my productivity gains at this point are going to come from faster input anyway. Sorry, vim, it's not you, it's me.
  - Agentlien 6y ago
    That's one of the strengths of Vim, though. There's a lot of structure to it, so you don't need to learn nearly as many shortcuts as you otherwise would.
  - 40four 6y ago
    I’m a full time vim user now, and I would say the ‘productivity’ gains are a bit of a pipe dream. That’s not the reason I would recommend anyone learn vim. The best reason for me is that vim is just fun. When you finally become competent, it is an absolute joy to work with. It makes me think about editing in a totally different way. However the road to get to that point is not fun. I started out with basic tasks in the terminal, & vimtutor reps. Then graduated to using a VS code plugin. I would turn it on for 10-15 minutes at a time a few times a day. Usually turning it off once I realize I wasn’t getting anything done :) But solid reps everyday over a few months and I got to where I learned more complex commands/ movements. Eventually I never needed to turn it off! Then I began the configuration & plugin rabit-hole :)

mhaberl 6y ago

For anyone wondering, you use it by executing vimtutor in terminal (not in vim). Also, you exit by pressing ESC and then typing :q (hit enter)

libria 6y ago
How fitting that the tutorial for vim needs its own pre-tutorial for exiting.
- Izkata 6y ago
  It's also in the tutor, lesson 1.2 But there's actually nothing special about vimtutor here: all it does is write a temporary file and then open it in vim.
- samstave 6y ago
  Before replying to your post I upvoted, I had to hit a link called [REPLY]
- alfiedotwtf 6y ago
  Having seen machines that have hundreds of Vim sessions opened because “system integrators” didn’t know how to exit Vim, it should be the very first thing taught
  - johannes1234321 6y ago
    Luckily vim finally got a bit better with that: on a Ctrl-C newer versions now show instructions for quitting. I remember my first vi sessions (typically via something like `crontab -e` where it wasn't clear to me it picked my "default" editor ... thus didn't know where to read up on it ...) some long time ago, where i knew `kill` before the right command ...

CoffeePython 6y ago

Yep I’d definitely recommend the same, vimtutor is great.

kkoncevicius 6y ago

first vimtutor and then :help user-manual

gbrown_ 6y ago
Yes! Sadly a lot of people skip over this despite vimtutor pointing to it at the end. Copy/paste below as the text doesn't need paraphrasing, but also because a lot of comments here seem to be advocating vimtutor as something more than the "brief overview" it is. This concludes the Vim Tutor. It was intended to give a brief overview of the Vim editor, just enough to allow you to use the editor fairly easily. It is far from complete as Vim has many many more commands. Read the user manual next: ":help user-manual".
40four 6y ago
The vim help files are fantastic. Well written, and clearly explain any feature you need to understand better.

rjvir 6y ago

Looks like "vimtutor" is primarily text explaining the hotkeys. For me, the bottleneck to picking up vim has not been merely knowing the hotkeys, but more internalizing the commands and building muscle memory. The interactive game format of this website could possibly solve that, so it appeals to me.

pksebben 6y ago
vimtutor is designed for you to use it regularly to train muscle memory
- D2187645 6y ago
  Vimtutor is free so you are the product.
  - Maha-pudma 6y ago
    So is Vim
baconsteakey 6y ago
It says this in the 3rd or 4th paragraph: > It is important to remember that this tutor is set up to teach by use. That means that you need to execute the commands to learn them properly. If you only read the text, you will forget the commands! And it's free, not 15 USD or whatever this site is charging.
- ketzo 6y ago
  Okay... but the difference between a piece of text just telling me to use the commands so I remember them versus an interactive trainer that provides a structured setting for me to use them is pretty significant, no?
  - boogies 6y ago
    > a structured setting for me to use them is provided by vimtutor. I wish people would take a couple hundred milliseconds to research things like this before posting about them — most [GNU’s Not] Unix commands take less time to run than a webpage takes to load, and installing their packages takes no more typing than a web search.

scottmcdot 6y ago

vimtutor might be a little too intimidating compared to a vim course in a browser.

ajfjrbfbf 6y ago

I started with vimtutor, then installed IdeaVim in all my Jetbrains IDEs, it took me about a week to reach the same level of efficiency I had before. I don't understand how some people can say the learning curve is too steep. Sure it's a bit annoying at first, but it quickly becomes natural, and you don't have to use all features at first. It has allowed me to improve my touch typing a lot. Learning a programming language is a lot more work but hardly anyone ever complain about it. It's been maybe two months and I wouldn't think of using anything else than vim for serious code editing.

sverhagen 6y ago
> I don't understand how some people can say the learning curve is too steep I am doing fine with vim for basic editing tasks and use it a lot (mostly when I'm already in the command line). But there's just only so many shortcuts I'm capable of memorizing. This is not a problem for me exclusive to vim, of course. In IntelliJ I also sometimes find an amazing new function that I then don't keep using since I've already exhausted my limited "inclination" of learning new shortcuts. Also, I don't think my productivity gains at this point are going to come from faster input anyway. Sorry, vim, it's not you, it's me.
- Agentlien 6y ago
  That's one of the strengths of Vim, though. There's a lot of structure to it, so you don't need to learn nearly as many shortcuts as you otherwise would.
- 40four 6y ago
  I’m a full time vim user now, and I would say the ‘productivity’ gains are a bit of a pipe dream. That’s not the reason I would recommend anyone learn vim. The best reason for me is that vim is just fun. When you finally become competent, it is an absolute joy to work with. It makes me think about editing in a totally different way. However the road to get to that point is not fun. I started out with basic tasks in the terminal, & vimtutor reps. Then graduated to using a VS code plugin. I would turn it on for 10-15 minutes at a time a few times a day. Usually turning it off once I realize I wasn’t getting anything done :) But solid reps everyday over a few months and I got to where I learned more complex commands/ movements. Eventually I never needed to turn it off! Then I began the configuration & plugin rabit-hole :)