24

Holy shit! It's so easy and accesible. The best part is that it's simpky build in to linux (or wsl). It's just a terminal command "vimtutor".

I'm astonished that nobody has ever told me about this before.

top 3 comments
sorted by: hot top new old
[-] pinball_wizard@lemmy.zip 4 points 5 days ago* (last edited 5 days ago)

I'm astonished that nobody has ever told me about this before.

I mean, it is right there in the welcome screen - where I, myself, foolishly ignored it for six years.

So now I also try to tell people about it. Haha.

It really is great.

[-] ruuster13@lemmy.zip 2 points 5 days ago

Does anyone know of a package directory for these types of things? Something like octopi for apt.

[-] Paragone@lemmy.world -2 points 5 days ago

While true, as an old Vim user, I'm recommending finding some other modal-editor: too much cruft in Vim.

I hear Helix is modal.

( modal-editors help bash one against one's unconscious-mind's woodenness: forcing switching-of-levels, & if you read "The Design of Everyday Things", which Adam Savage also recommends people read, as he found it life-changing, then you'll read that NOT-switching-levels is a racial mental-defect: we just enforce-harder, instead of switching-levels, & break opportunity we're in!

So, modal-editing helps break that ignorance, giving us better ability to get out from the wrong-level into the right-for-the-context level, & therefore I absolutely recommend modal editors, for nearly-all.

However, vi & vim .. a bit too much cruft, in the crystallization.

Clean-slate optimization of what commands are in, what key-codes are for what, etc, ought produce a better tool. )

_ /\ _

this post was submitted on 20 Mar 2026
24 points (100.0% liked)

Learn Programming

2137 readers
1 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago
MODERATORS