Many people do that: “Literate configuration” is quite popular in the Emacs world, where you basically write your config as a “document with code blocks” instea

Many people do that: “Literate configuration” is quite popular in the Emacs world, where you basically write your config as a “document with code blocks” instead of a “code file with comment blocks”. For a well-crafted example, see e.g. [tecosaur’s config](https://tecosaur.github.io/emacs-config/ https://tecosaur.github.io/emacs-config/). Part of the problem is that Emacs configs have traditionally grown much larger than the typical Vim/Neovim config :)