Vi and Vim Stack Exchange is a question and answer site for people using the vi and Vim families of text editors. It only takes a minute to sign up.
Sign up to join this community
One big difference of neovim and Vim is that neovim includes a terminal emulator that works asynchronously.
However, I fail to see how can I profit from this feature. For what can I use it? Can you give some use cases for neovim's terminal feature so that I understand how I can use it to its best extent?
In normal Vim I normally use :read !{command}, :write !{command}, Ctrl+Z and fg as well as tmux split windows.
Running a terminal inside Vim allows you to use Vim commands on the input and output to the programs that you run in that terminal. You get search, copy-paste, macros, syntax coloring, etc. Using :read !{command} and :write !{command} gives you that for one-shot commands, but asynchronous input/output becomes useful when you want to submit input to an external program piece by piece.
The typical use case is a read-eval-print loop (REPL), which is provided by many high-level programming languages. You type a stanza in your source code, then feed it to the REPL for immediate feedback. Since the REPL keeps running from one submission to the next, the submitted code snippet are executed in context.
I think the option to create terminal-only mappings is valuable, and extends the options you've got in other terminal emulators, e.g. mapping t to run unittests with specific configuration, which you can only achieve through complex aliases or bash functions.
The most obvious use case I can think of is programming. Have you ever wanted to run tests inside Vim, or compile, or use any console tool? I know people use Tmux, but now that you can do it inside Neovim I have to say, this is pretty awesome.
If you use buffers you can add, remove, hide and show terminals as you please. That's the profit ;)
The best use case I can think of is the original one-an ADM-3a on a 110 bps line! Sometimes there's really no substitute for looking at things side-by-side, and :!r doesn't cut it.
One particular use case I had experienced was conservation of my development environment in a different terminal emulator. At the time, I needed to change my terminal emulator to xterm which does not support tabs, as far as I know. I was use to having this feature from gnome-terminal. However with a terminal emulator inside neovim, I was able to open new tabs inside neovim and launch terminal emulators from there, thus mimicking closely my old work environment.
tmux or screen might be more appropriate. The main advantage of using it from Vim/NeoVim (over those tools) is deeper integration with the editor, such as splitting between editor and terminal (doable in tmux/screen, but cleaner with Vim/NeoVim terminal) and launching commands from the editor, such as building or running code from current buffer.
<C-z>is that the Vim process is suspended by the OS: it's not doing anything (including responding to server commands).:shellwithexitinstead or is vim suspended here too?<C-z>, that's a problem with your script.