News for hackers. Stuff that matters.
Re:A Vim Guide for Advanced Users by janvdberg on Thursday December 01, 2022 @06:28AM (#33814947)
I keep this URL in my bookmarks: https://jemma.dev/blog/intermediate-vim-tips

Most advanced guides throw a lot at you at once. Digesting one or few commands at a time works better for me to really make it stick (and that is the goal right?)

Re:A Vim Guide for Advanced Users by SnooSux on Thursday December 01, 2022 @10:03AM (#33817104)
If I could add one thing to the list I would include `cib` as equivilent to `ci(` for changing everything in a set of parentheses (or brackets for the mnemonic's sake). For me at least the `b` is easier to reach than the `(`.

I need to use `z` for refocusing more

Re:A Vim Guide for Advanced Users by koningrobot on Thursday December 01, 2022 @10:31AM (#33817569)
I notice it mentions Ctrl-a and Ctrl-x which "increment or decrement any number after the cursor on the same line". I hate these shortcuts because several times I've accidentally pressed them (e.g. on some level thinking I'm in Spacemacs or in readline) and introduced a hard-to-find bug into my code without knowing it.
Re:A Vim Guide for Advanced Users by quesera on Thursday December 01, 2022 @11:38AM (#33818684)
Agreed. I love vi, but this is almost always an anti-feature.

To disable, add these lines to .vimrc:

  map <C-a> <Nop>
  map <C-x> <Nop>
Re:A Vim Guide for Advanced Users by civopsec on Thursday December 01, 2022 @12:38PM (#33819604)
Won’t you spot that through you source control?
Re:A Vim Guide for Advanced Users by srik on Thursday December 01, 2022 @09:43PM (#33826090)
Shows how crucial customizability is because I don't think I can work without being being able to rely on <c-a/x>, and more importantly g<c-a/x>.
Re:A Vim Guide for Advanced Users by jcul on Friday December 02, 2022 @04:42AM (#33828565)
They can be quite useful, but I just stopped using them due to muscle memory of Ctrl-a for screen / tmux.
Re:A Vim Guide for Advanced Users by michael_j_ward on Thursday December 01, 2022 @11:12AM (#33818245)
Having suffered through learning highly configurable software tools independently enough times, I agree completely with "digesting one or few commands" at a time works better for me too.

Spitballing:

We could probably make a general solution for organically producing "learning guide" if power users 1) share their custom configurations and share the frequencies of commands they use.

Start with the general configuration, knowing nothing about the commands the tool offers. The learning guide is just a queue of "here's the most common config edit that you don't have" and "here's the most common command that you don't know about."

We are already share configs with eachother via the dotfiles pattern. We somewhat share command patterns via coding streams. Seems doable.

(In general, making it easier to learn new tech and for devs to share / refresh the learning material for a new tech seem underdeveloped.)

Re:A Vim Guide for Advanced Users by thanato0s on Friday December 02, 2022 @02:30AM (#33827861)
I agree. That said, I also like to have a more complete guide and pick and choose what could be useful for me.