I’m going to come clean right off the bat. The title of this post is my half-hearted attempt at clickbait: what you are about to read can’t reasonably be described as a security issue. It barely even qualifies as advice, in that the thing I intend to demonstrate you should NEVER DO is something you didn’t have any plans to do in the first place. It’s really more of a fun curiosity, and yet another entry in my series of weird things you can do with macros.| Normal Mode
Vim help pages, always up-to-date| vimhelp.org
Vim help pages, always up-to-date| vimhelp.org
Symbol inspection tools for w64devkit: vc++filt and peports| nullprogram.com
Vim help pages, always up-to-date| vimhelp.org
Vim help pages, always up-to-date| vimhelp.org
Vim help pages, always up-to-date| vimhelp.org
I’ve never done Advent of Code before, and I wasn’t planning to do it this year1, but for some reason I decided to try my hand at solving the 2023 event’s Day 1’s challenges in Vim, using only its editing commands. (So ex commands are allowed, but Vimscript’s more programmerly constructs — functions, loops, conditionals, etc. — aren’t.) It was fun! So much fun, in fact, that I ended up carrying on and completing a bunch more of the challenges.| normalmo.de
Vim help pages, always up-to-date| vimhelp.org
Vim help pages, always up-to-date| vimhelp.org
I was trying to write a Vim function that would act on a visual selection but found it surprisingly difficult. — can be read in 2 minutes| til.codeinthehole.com
Vim help pages, always up-to-date| vimhelp.org
Vim help pages, always up-to-date| vimhelp.org
Vim help pages, always up-to-date| vimhelp.org
Vim help pages, always up-to-date| vimhelp.org
Vim help pages, always up-to-date| vimhelp.org