Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 1
    While this is a fine way to learn new commands, it's sub-optimal for getting faster, which is what the OP is wanting to do. Sub-vocalization slows you down because it restricts you to the speed of speech. Commented Oct 24, 2022 at 20:56
  • 1
    @MDeBusk Re: speed of speech. Eventually text editing thoughts go straight to your hands vocalizing vim commands to the keyboard. It's like a bilinguist starting with thinking in their primary language, translating, and then speaking in their secondary language. Eventually with practice, their mouth will start outputting their secondary language without their brain involving their primary one at all. It's the same thing, only with your hands instead of mouth. Commented Oct 24, 2022 at 22:52
  • 1
    @JoL "Eventually", maybe. If you unlearn subvocalization. Most people don't, because they don't even realize they do it. Research has consistently shown, too, that translating from one's native language impedes acquisition of foreign languages; we're better off learning foreign vocabulary the way we learned our native vocabulary. And I'm pretty sure we're now off-topic. Commented Oct 25, 2022 at 0:12
  • 2
    Could you expand a bit on how that cs([ command works? I can't find anything about it in the helpdocs, and I can't make it work in my version of Vim (or Neovim for that matter). Commented Oct 25, 2022 at 13:38
  • 4
    cs is defined in Tim Pope's vim-surround plugin - github.com/tpope/vim-surround. It's very helpful for adding, changing or deleting "brackets" of all sorts around a text object or motion. Commented Oct 25, 2022 at 18:47