reportaman wrote: > > The document, which is admirable, is still not reassuring for real world > workload in terminal emulator built into Vim.
> I came across a neovim plugin page, that says it is not recommended > to run long jobs within terminal emulator built inside neovim as that can > slowdown neovim experience. Is that expected to be the case with Vim's > implementation/handling of internal terminals? If yes is there a way to > not affect a slowdown while running multiple terminal instances that are > heavy. Probably the same in Vim. I assume it's because Vim or neovim are not multi-threaded. Starting a terminal with a job that keeps printing on the terminal makes Vim slow indeed, to the point of being almost unusable. Just try this: :terminal yes test Then press CTRL-w CTRL-w to go to the regular buffer and notice that Vim is slow. But this is not a common scenario. Generally, running regular commands in the Vim terminal is fine. Regards Dominique -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAON-T_gg00EdW3rxZb0bVh3uNzUWCaefAmgiKr%2BR-JdQ3SLwbA%40mail.gmail.com.
