I don't use it that often (I just open up another terminal), but you can also use ^Z to put vi in the background. It would be more useful if I didn't always forget and open up a new vi which would refuse to write to the file :)
The integration is nice, it behaves as a normal buffer. So you can use all the standard modes and motions, splits, copy output to another buffer easier etc.
what got me to switch was being able to run terminal commands in a buffer...
https://neovim.io/doc/user/nvim_terminal_emulator.html
I don't use it that often (I just open up another terminal), but you can also use ^Z to put vi in the background. It would be more useful if I didn't always forget and open up a new vi which would refuse to write to the file :)
I honestly do both. When I'm running something I want the output from (some to yank), I'll run in a buffer.
If doing file manipulation, CLI, etc. etc. I'll ctrl-z out.
I do the opposite of you pretty often too, always trying to `fg` a non-existent vim
1 reply →
Serious question: why not just open another terminal?
The integration is nice, it behaves as a normal buffer. So you can use all the standard modes and motions, splits, copy output to another buffer easier etc.
2 replies →
You can use it as a normal buffer. Run command, switch to visual, go copy and paste. Way nicer than `:r !command`.
You can use :terminal in vim.
it's optional for the build: https://vimhelp.org/terminal.txt.html
Only if you want very specific plugins.
Not really. vi doesn’t have some very basic motions that are supported by (n)vim out of the box.