black

It does, you'd just have to install a python plugin that registers the autocommand-- or leave out the plugin and register the autocommand yourself. The (n)vim/emacs communities aren't fond of integrating the hot new thing for each language directly into the editor-- I think this is a lesson that comes from being 50 years old! As for whether it would be buggy, I'd doubt it? Unless Black's principle of operation is different from most formatters, it should just write the formatted contents to the file, right? The autocommand you'd use would just run Black on your current file on each save. So where % is Vim's symbol for the name of the currently open file, :silent! suppresses stdout/stderr from the formatter, and :! runs a command: autocmd BufWritePost *.py silent! !<format_cmd> % (Don't quote me on that, but it should be essentially correc

Python formatter Black: https://github.com/psf/black By using Black, you agree to cede control over minutiae of hand-formatting. In return, Black gives you speed, determinism, and freedom from pycodestyle nagging about formatting. You will save time and mental energy for more important matters. Black makes code review faster by producing the smallest diffs possible. Blackened code looks the same regardless of the project you’re reading.

Python does have an auto-formatter [6], so clearly indentation doesn't prevent that. > Also, forget a brace in your program, just one, and the compiler can tell. Should we duplicate every character, so the compiler can tell if you leave one out? This is not a radiation-hardened quine [7]. > editor settings can make it much easier to break things with significant whitespace. Then use an editor which doesn't. > Selecting all code contained in a brace or a parents is so much easier (in vim the % movement) than if you have to walk lines. I have a plugin for Neovim that adds indentation-based motions. The implementation is trivial. [6] https://github.com/psf/black [7] https://codegolf.stackexchange.com/questions/57257/radiation...