Yatao Li
Yes I think this is a preference, and our current implementation complies to the nvim defaults (terms are listed). You can use something like [https://github.com/yatli/vmux.vim](https://github.com/yatli/vmux.vim) to automatically unlist the terminal...
@corbob `nmap` does this. If someone writes `nnoremap`, then `nmap` to the same keys will be ignored.
@TylerLeonhardt it's hard to find VS binding fans (like me :D ) in the wild these days, do you have ideas about the VSCode keys? I can implement them.
No need to provide a vimL file, because we can execute vim commands from typescript
[coc.nvim] Error on active extension coc-powershell: TypeError: (intermediate value) is not iterable
`coc.nvim` uses different mechanisms for `vim` and `nvim`, to start terminals -- `jobs` for `vim` specifically. I've just tested with `gvim.exe` and here's what happens on `:q`:  Here's `:bd`:...
[coc.nvim] Error on active extension coc-powershell: TypeError: (intermediate value) is not iterable
@TylerLeonhardt in addition to `activate`, we need to tear down the language service with a `deactivate` method. That's the place where we should destroy the terminal (and thus the job)....
tracking: #47
Yes!
Curious, what's the difference between showHelp and onHover? A few VSCode extensions now support "info pane" which places help info in a persistent window -- guess showHelp is similar? Edit:...
thanks for the explanation. I just played with it for a few commands, but it keeps landing on a 404 page. For example: `Get-Help -Online Get-ChildItem` gets me: https://docs.microsoft.com/en-us/powershell/module/4.0/microsoft.powershell.core/providers/FileSystem-Provider/Get-ChildItem-for-Filesystem