Everything you ever wanted to know on how to execute a command in multiple files in Vim. I mostly use argo and cdo. #vim

TIL that there are some interesting C programming tips on Neovim wiki. #vim #clang

Interpretable Machine Learning: A Guide for Making Black Box Models Explainable.

No more nvim-lspconfig means 15 ms less time spent in starting up! #vim

TIL that you can clear your Tmux paste buffers by tagging everything (C-t) then deleting it (D).

Pytest is really great: even simple assert statements get processed, no need to write complex fixtures or test suite. This means you can write your scripts as usual and just import pytest. To avoid contaminating your current directory with __pycache__ and .pytest_cache directories, set the exported variable PYTHONDONTWRITEBYTECODE=1 and call pytest with -p no:cacheprovider. You can set a simple compiler and errorformat for (Neo)vim by following this blog post. Personally, I use makeprg=pytest\ --tb=short\ -vv\ --no-header\ -p\ no:cacheprovider\ $* instead. #python #vim

If you are using vimtex and are interested in using Evince for forward/reverse synchronization, be sure to check sved which at least provides reverse sync in Neovim. Otherwise, Zathura works as expected. #vim

Ergonomic mappings for code formatting in Vim: Very nice tutorial on code formatting and how to write VimL functions that exploit gq. #vim

OpenBSD Handbook. #unix

But let’s just put it this way (and here I’m being charitable): in all my years of using Word, this happened more than once. In all the time I’ve used text editors, it’s never happened, even once. — Why (and How) I Wrote My Academic Book in Plain Text