:term

[trusktr]

It might be neat to support this. The main advantages of this would be that we would have the same vim-style navigation and workflows in the terminal (move in NORMAL mode, select text in VISUAL mode, etc, unlike in VS Code's terminal panes), and we could have multiple terminals in VS Code window splits. It would not be exactly like neovim's, due to window/tab differences, but gets closer than VS Code's pane.

At the moment, it is a little funny: Running :term actually seems to make a new terminal, but the VS Code buffer does not update to that new buffer. When pressing i to insert into the invisible terminal, the VS Code cursor does indeed move to the new place where the command line would be. Then to exit the terminal, pressing <leader>n to exit terminal insert mode works but also makes a new empty VS Code tab. Switching back to the previous tab and pressing any key, coincidentally, returns everything back to normal and we can continue editing the VS Code buffer with Neovim comands.

[theol0403]

For what it's worth, earlier versions of this plugin properly showed the terminal buffer. Not completely usable, but kind of cool.

[asvetliakov]

also something like PlugStatus worked too. Neovim originated external buffers can receive ton of improvements, especially with new custom editors vscode api.

[saidelike]

May I ask how difficult it would be to have the terminal in Neovim actually working (using the :term command?

It would allow supporting cursorless (accessibility/automation, see https://www.cursorless.org/) directly in the terminal (since it works on the text editor)

I can confirm on Windows that nvim.exe spanws a cmd.exe and the commands are executed. It is just that it does not display the buffer. For instance I blindly typed dir C:\tmp in the example below: