1

I'm working on a fairly large project and often have multiple buffers (and windows) open at the same time. Now whenever I would do a :windo w! or :bufdo w! to save all open files, vim uses 100% cpu power as shown by top and completely blocks cursor movement and basically becomes unresponsive until all buffers/windows are saved.
How does this make sense? Why isn't saving of loaded to another thread/core so that browsing & reading files still work while saving is going on?
I'm wondering if there is a particular reason why it was implemented this way?

closed as primarily opinion-based by Rui F Ribeiro, Kusalananda, Satō Katsura, G-Man, mdpc Jan 26 '18 at 1:08

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

Browse other questions tagged or ask your own question.