: for vim professionals

Vim, as practiced.

Understand the config you already have, see which parts you actually reach for, and get measurably better at the editor you live in. Read the configs you admire the same way — line by line, as they really are.

Start a drill → see what's in real configs →

Connecting your dotfiles is in early access — a small number of people while the tool finds its shape. One repo, read-only, private is fine. We read your config; we never run it.

init.luaexplained

36nmap(';', ':')

command mode on an unshifted key — a considered trade

7{ 'nvim-telescope/telescope.nvim' },

lazy-loaded on :Telescope · 4 of your mappings reach it

21vim.o.clipboard = 'unnamedplus'

the clipboard as unnamed register · :help 'clipboard'

NORMALwe read it; we never run it

three ways in

01Your vim

Every line explained, versioned by its own git history — and which parts you actually reach for.

:e connect your dotfiles

02Other pros

How other people solved the problems you have, read from their real configs — including the starter kits many configs begin from.

:g usage:t templates:vs compare:w feed

03Practice

A technique a day in real vim, compiled to the browser. Nothing to sign up for — just the drill.

:z today's drillgd the techniqueu undo, retry

try it now · nothing to sign up for

One technique at a time.

Each drill names one technique and shows you its shape, then asks you to use it on real text — in real vim, the same engine your terminal runs. Using the technique is the point, so that's what counts.

start a drill →

Nothing to sign up for. Every drill names the technique up front, so you always know what you're learning.

#0001Ship it cleanpractice

1code1()

2DEBUG: trace 1

3code2()

4DEBUG: trace 2

5code3()

6DEBUG: trace 3

puzzle.txt

1code1()

2code2()

3code3()

4code4()

5code5()

6⋮

[target] read-only

the technique · the global command the shape, never the answer · :g/pattern/cmd

NORMALmake the left buffer match the right one

fingers.nvim · the editor half

Your config says. Your hands do.

This site reads what your config sets up. fingers.nvim sees what you actually press — on your machine — and tells you where there was a shorter way.

Drill a technique here, and it will tell you whether the drill reached your real editing — the practice record comes from this side, the keys are counted on yours.

fingers.vim.pro → then drill something →

A separate plugin that works with the network unplugged. Nothing to sign up for, and everything stays on your machine — it reads from here, and only reads.

fingers://you:Fingers

drilled, then 2 of 5 reached your editing

visual-block drilled 9d ago ×9 since

increment drilled 1d ago not once since

NORMALcounted locally; nothing has left this machine

Measure your own editing.

Do both. The drills teach you a technique in twenty seconds; fingers.nvim is what tells you, a week later, whether it reached your real work.

Practice in real vim → Install fingers.nvim →

Both work right now, with nothing to sign up for. Connecting your dotfiles is early access.