Tyler James Leonhardt
Tyler James Leonhardt
> Does this separate process has any kind of limitation when if comes to how 'OK' button with event handler will work? You'll need to set up the event handler...
Apologies, I'm not sure I understand the question.
Including it in PowerShell won't change anything, unfortunately. The problem is because PowerShell runs PowerShell script on a background thread, rather than the main thread. MacOS doesnt allow gui code...
Also we'd basically double the size of PowerShell if we included Avalonia as a dependency. Which is sadly a non-starter
I was hoping such a change could be done in https://github.com/PowerShell/PowerShell/pull/10962#issuecomment-551910972 Which introduces a `pwshw` But it would have to be a separate PR
@ALIENQuake this was the code change in PowerShell itself... but the risk of doing that was unknown so we didn't take the change. https://github.com/SteveL-MSFT/PowerShell/commit/41c3b0f3a41eb5d7897339cb22cad26c0a801c9f
coc-powershell is still in early days. Apologies for the lack of docs! The `powershell.integratedConsole.showOnStartup` issue sounds like a bug. We should track that in a separate issue
PowerShell's language server does not support renaming at this time... upstream: https://github.com/PowerShell/vscode-powershell/issues/261
you can set this setting: ``` "powershell.integratedConsole.showOnStartup": true ``` or use the CocAction `powershell.toggleTerminal`
Like you said, all of the language features come from the Integrated Console if you get rid of that, then you don't have any of the goodness that coc-powershell provides....