sanitizers VS dotfiles

AddressSanitizer is really useful, it's similar to Valgrind but has much lower overhead.

And if you're up for it, I'd further recommend adding some ways to deal with buffer overflows in debug builds. The way I deal with this is by using Address-Sanitizer's manual poisoning api. Bonus point if you leave additional poisoned space between allocations so off by one errors are likely to end up in a poisoned region instead of nearby allocation.

It also doesn't hurt that Miri can find many kinds of unsafe violations even in unsafe blocks. Zig may get something like this one day, but even if it does, checking things at runtime is not a substitute for compile time -- the C++ Sanitizers haven't exactly solved the safety story for C++ even over a decade later.

This is where stuff like ASan is really useful.

Use: https://github.com/google/sanitizers/wiki/AddressSanitizer

Have you tried using tools like ASAN/LSAN or valgrind to confirm that there are indeed no memory leaks?

Compile with ASAN and UBSAn

I've just noticed my vimrc right now has exactly 600 lines... not counting the rest of files of course

I only really needed to set few settings + extend syntax folding to comfortably write Markdown

And I don't know anything about stow as I just use my own simple install script

I have public GitHub repository with all my dotfiles under MIT license. On private machine I make changes to them; on work machine, I just clone/pull that public repo. Eventual changes done during work time I just remember to implement at home again.

Like this one I have in my dotfiles?

Well, I'm not gonna comment every tiny bit (as it's usually obvious from the code already), but if you are interested in reading others configs: my vimrc alongside the rest of my Vim configuration

Arch Linux (or WSL2 on Windows)

You start like this and end like this ;)

Read configs of more experienced users (here's Jorengarenar's, for example)

I use vim-lsc (my config)