←back to thread

VIM Master

(github.com)
378 points Fluffyrnz | 8 comments | 27 Aug 25 15:50 UTC | HN request time: 0.001s | source | bottom
Show context
benjaminclauss ◴[27 Aug 25 17:14 UTC] No.45042331[source]▶
These little tutorials and games are great. I played VIM Adventures.

However, one thing I really struggle with is learning when I can be doing something more efficiently. I rarely use markers, anything beyond default registers, commands, and so on.

I'm giving Neovim a try for my systems course trying to get better but I do wish these sorts of games pushed me to get better at these more advanced usage tricks.

replies(5): >>45042781 #>>45045030 #>>45045601 #>>45046143 #>>45047599 #
1. soperj ◴[27 Aug 25 17:54 UTC] No.45042781[source]▶
Oh man, I use markers all the time. ma y'a

mark a spot, then yank or delete everything to that line. Way easier to do it accurately rather than 13yy or however many lines you're yanking.

replies(3): >>45043100 #>>45043375 #>>45050754 #
2. zeke ◴[27 Aug 25 18:19 UTC] No.45043100[source]▶
You can use <shift>v then move to your start line and type y or d. This way you see the text marked before yanking or deleting. <control>v is similar. And gv will reselect the marked area.
replies(1): >>45043228 #
3. dwater ◴[27 Aug 25 18:30 UTC] No.45043228[source]▶
And if you have line numbering on you can y123G. I learned enough Vim 25 years ago to be good enough and I'm happy I did. When I was writing code every day I picked up a little more but I've lost most of it, and what I'd want people to know who are considering it is you never need to be a Vim Master. You can learn enough Vim in 30 minutes to make it beneficial to you for the rest of your life.
replies(1): >>45045645 #
4. ramses0 ◴[27 Aug 25 18:41 UTC] No.45043375[source]▶
ma, mb, mc => 'a, 'b, 'c => ...just being able to "tag" each of the three functions you're working with (comparing, copying, moving code, whatever) it's eventually worth it to get them into your muscle memory. And once you "get" marks, then you "get" registers "for free".
replies(1): >>45045189 #
5. soperj ◴[27 Aug 25 20:58 UTC] No.45045189[source]▶
and this is why i always read vim articles... i've never used registers in my life.
replies(1): >>45047879 #
6. Izkata ◴[27 Aug 25 21:40 UTC] No.45045645{3}[source]▶
I turn on relative line numbering so that y123G might be y8j and vim will show me the 8.
7. ramses0 ◴[28 Aug 25 03:01 UTC] No.45047879{3}[source]▶
I'll use them in macros fairly frequently: vawy'f => function name, vi{y'b => body, vi(y'a => args

...or y'x to keep something kindof handy that I can drop in at the right place (sometimes with a macro...)

    qadi('xpq => @a => @@...
(Record macro "a", delete inner parentheses, paste from the "x" register, stop recording => play macro "a" => play last macro...)

If I keep "x" clean/protected then I can delete or edit the rest of the time all willy-nilly and not worry about clobbering what I'm trying to paste into the right spots.

8. asimovDev ◴[28 Aug 25 11:11 UTC] No.45050754[source]▶
I feel so damn stupid for counting the lines with my eyes before yanking after reading this. As a staunch believer in markers, this is eye opening. I was using them just to jump between functions most of the time. This is very useful