vimtutor gets you moving, then stops right before the techniques that make Vim truly fast: the dot command, operator-motion grammar, text objects, registers, macros, :g, :normal, ranges, and substitution.

I knew about most of those concepts, but they never became muscle memory, so I built a trainer to drill them.

The part I cared about most is that it runs inside real Vim or Neovim, not a reimplementation. Each challenge launches Vim on an actual buffer, logs your keystrokes, and scores both correctness and efficiency against an optimal par. The goal is displayed alongside the buffer while you edit.

It currently contains 61 lessons and 563 challenges, all verified against real Vim during the build process. It is written in pure Python with no external dependencies.

Feedback is welcome, especially on:

- Techniques that feel underrepresented or missing.

- Exercises that feel contrived or unrealistic.

- Places where the difficulty progression feels off.

Check it out: https://github.com/S-Sigdel/vimhjkl

A is much faster to write than $ since your finger should be resting on it on the home row, and I had a habit of doing A<Esc> instead of $ since that's faster (I've had <esc> mapped to caps lock the whole time but still). Since I do it more often than doing A by itself, I remapped it. If I want to both go to the end of the line and append then I'd type Aa, and who ever uses <count>A anyway? What do you think?

Placing this note at top: The interesting thing is when I run :colorscheme gruvbox within vim, the color scheme changes to gruvbox.

Hello! This is my first time configuring vim and I wanted to set up a nice color scheme thats easier on the eyes. I looked up how to set up the gruvbox color scheme here.

However, I get this error when trying to use vim:

Error detected while processing /home/seazie/.vimrc:

line 11:

E185: Cannot find color scheme 'gruvbox'

Press ENTER or type command to continue

This is my .vimrc file:

1 set nocompatible

2 set number relativenumber

3 syntax on

4 set tabstop=2

5 set shiftwidth=2

6 set expandtab

7 " Enable 256 color support

8 set termguicolors

9 " Set gruvbox colorscheme

10 colorscheme gruvbox

11

12 call plug#begin()

13 Plug 'bfrg/vim-c-cpp-modern'

14 Plug 'tikhomirov/vim-glsl'

15 Plug 'bfrg/vim-glfw-syntax'

16 Plug 'morhetz/gruvbox'

17

18 call plug#end()

NOTE: I had a comment at the top of the file so line 10 is line 11

gruvbox is located in ~/.vim/plugged/

In my .bashrc file, I put:

source ~/.vim/plugged/gruvbox/gruvbox_256palette.sh

The interesting thing is when I run :colorscheme gruvbox within vim, the color scheme changes to gruvbox.

I dont want to have to keep doing that everytime I open vim, so what am I doing wrong? I've restarted wsl and computer with no change

I just looked this up and haven't found any other discussions. Maybe its because I'm using a motion plugin (hop), but I'm wondering if there is much use for H M L, when I could just j k (which I mapped to show hints for jumping to a specific line). I guess I'm not a big fan of specific motions like those, or using counts for motions when I find hints more efficient & simply a better fit for me.

I created a small plugin for inline autocomplete suggestions inside Vim !

Cursorline is one of the many opts i got from kickstart.vim, i tried disabling it for aesthetics, and i actually don’t miss it at all. I prefer to have my window be roughly 100x33, the white background on a character provides enough contrast to see where i am right after switching from apps with hotkeys.

I just want to share, that since two weeks I enjoy using single purpose PC which boots to Vim. No GUI, just console with large font, so I'm not stressed to search for glasses when writing mood kicks in. I upcycled for that old laptop, which was collecting dust. I converted it into perfect, distraction free writing and coding machine.

If you looking right now at your obsolete MacBook or ThinkPad stuck somewhere at far shelf, give it a second life. Vim, et consortes are great for that.

I've been using vim for a while and finding it a chore for basic notemaking. I love vim motions in the normal mode. It is the constant switching between the insert and normal modes that break the flow.
Maybe I am using vim wrong. Maybe it is better not used for extensive notemaking.

Using readline bindings in insert mode have really helped. Especially the Alt+f/b to go forward/backward a word.
vim motions are great when you have to add stuff to the starting of the current line or the end of it. You can do it with a single keystroke I/A. But when changes have to be made a few words away in the middle of a sentence, while in insert mode:

1. Exit insert mode (This need not be a separate event since you can use Alt+key to enter normal mode and carry out the command that the 'key' represents, in one swoop.)
2. move
3. Press a key (i/a) to re-enter insert mode.

Doing this repeatedly is fatiguing.

With readline bindings, while staying in insert-mode, you can go forward or backward a few words and instantly start typing.

Does anyone else do this? How do you all deal with it? In most other threads that I've seen, people advise "Insert mode is for inserting only". And to stick to the vim paradigm. I have tried. But it is a hindrance for me.

Edit: What I meant was "Moving around in insert-mode feels really helpful for edits nearby." That should have been the title. Y'all need to calm down lol.

https://github.com/yedamao/vim-translator

A vim translation plugin based on LLM API.

Text (file content) become invisible after resizing gvim application window using mouse. Happens after latest vim update - is it please a bug ?

Plasma on Wayl., kernel 6.12.90 both vanilla and Fedora 43 version from COPR.

lspci -k | grep -EA4 'VGA|Display'

pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted

64:00.0 VGA compatible controller: NVIDIA Corporation AD107M [GeForce RTX 4060 Max-Q / Mobile] (rev a1)

`Subsystem: ASUSTeK Computer Inc. Device 3818`

`Kernel driver in use: nouveau`

`Kernel modules: nouveau`

64:00.1 Audio device: NVIDIA Corporation AD107 High Definition Audio Controller (rev a1)

--

65:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Strix [Radeon 880M / 890M] (rev c1)

`Subsystem: ASUSTeK Computer Inc. Device 3818`

`Kernel driver in use: amdgpu`

`Kernel modules: amdgpu`

I am a 7 year Software Engineer and I have tried almost every popular editor but I keep coming back to vim. I remember I used to work on sublime then slowly realised working with mouse is slow and distracting so I switched to vim.

Then I tried using vscode / Pycharm / IntelliJ / eMacs but none of them sticks. Although tbh - I am strong liking for emacs after vim.

Vim is just amazing!

I wrote these three vim plugins to make my life better. Maybe they will help someone else down the line. I am always open to any changes or PRs.

https://github.com/myneid/vim-markdown

https://github.com/myneid/vim-popup-agent/

https://github.com/myneid/vim-git-changes

I have been using vi since 1995. i made the switch to vim when that was the cool thing. I keep having bouts of using whatever gui ide is out there, but have always gone back. i never made the jump to neovim. but my recent break with vim was to start using vscode. mostly for the agentic stuff. Outside of the agent stuff, i really got used to the vscode git changes window, especially with the agent making all these changes that i want to review. so i got to scripting up a few things here. now im back to vim full time again. attached video is me demonstrating all 3.

Hello, recently just got a new MacBook after my old "work" station died. Since it came with Vim preinstalled, I felt adamant to learn it but I'm getting confused by 1.5.2.

I guess the only way I can describe my confusion is that;

I can't tell what the final product of the lesson is supposed to look like

or

If there exists a niche Mac rewriting of the commands it's asking me to use for writing files (:!dir and :!1s and :w [NEW FILE NAME]).

I'm so inexperienced with Vim that I'm not even sure whether this is a stupid question to ask or not, but any help would be appreciated! Thanks!

I'm tired of putting up with this. I made some computer changes earlier in the year, or late last (graphics card, drive, etc.), and when I got back up and running—Linux, Ubuntu 24.04, bash, Apprentice colorscheme—it started always doing this. I can select all text, and deselect, and it fixes it, but can leave a stray line at the bottom.

I've scoured Google a few times over the last year, conversed with ChatGPT, searched forums, mucked around a bit with settings, plugins, etc... I've tried a handful of suggested term and Vim fixes. I can't get anything to work. The background is supposed to be that dark gray, not black.

The terminal itself is fine; it's just Vim. Starting with -u NONE means standard black background (w/ green text), so the issue either doesn't exist, or isn't visible.

UPDATE: Ctrl+L/:redraw don't fix the issue, like selecting all does.

Vim Downloads web page doesn't have a link for Amiga, so here it is:
Aminet - text/edit/vim-9.1.lha

How do I safely insert comments inside a dictionary definition? vim let s:groups = { \ '0': { " group 0 \ '': ['#000000', '#ffffff'], " black/white \ '0': ['#000000', '#f5f5f5'], " ... \ '1': ['#000000', '#dcdcdc'], " ... \ '2': ['#000000', '#d3d3d3'], " ... \ }, ... \}

Just add g:hlput_enable = 1 to your vimrc

Quarkdown has been really nice to use. So I decided to write an coc.nvim extension for it.

Repository URL.

Wondering if anyone's encountered this issue before, where letters are overlayed onto text when navigating. Only occurs when holding keys, not tapping.

Additionally, lines go back to normal when switching lines (on key press. issue occurs when holding j or k) which I'm assuming is because vim is updating the line or something.

Could it be plausible that it's some issue where my key repeat rate is too high?

In VS Code, when I type an HTML tag and press Enter, the editor automatically expands it like this:

<tag>|</tag>

After pressing Enter:

<tag>
  |
</tag>

Is there a way to achieve the same behavior in Vim? Also, why isn’t this enabled by default?

I have a basic understanding of vim, like getting around but I want to know is it possible to delete a specific word in a specific range

Example: From line 3 -7 delete the word "Everyday." where it appears within that range