Closed ninmonkey closed 2 years ago
If the integrated terminal is actively doing something I'm pretty sure it blocks everything (intellisense, etc.), that's just one of those tradeoffs of having it be ISE-like I believe.
If the integrated terminal is actively doing something
@JustinGrote The PSIT is not blocking in this case. 100% of the time I have no semantic tokens. (Neither existing in the inspector, nor applying using my global super-bright colors config )
By autocomplete I meant Intellisense. (ie: it's not being blocked)
Addon | Version | Code | Version |
---|---|---|---|
ms-vscode.powershell | 2021-10-02 | insider | '1.64.0-insider', 'd12df34e31b4a018735d312a8947d79331132368', 'x64' |
ms-vscode.powershell-preview | 2021-11-01 | insider | '1.64.0-insider', 'd12df34e31b4a018735d312a8947d79331132368', 'x64' |
Addon | Version | Code | Version |
---|---|---|---|
ms-vscode.powershell | 2021-06-01 | code | '1.63.0', '7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e', 'x64' |
ms-vscode.powershell | 2021-10-02 | code | '1.63.0', '7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e', 'x64' |
ms-vscode.powershell-preview | 2021-11-01 | code | '1.63.0', '7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e', 'x64' |
Since code
is failing but powershell-preview
and powershell
both work correctly on code-insiders
, I'll close this as resolved.
Great detective work @ninmonkey :)
Oh awesome, thanks so much @ninmonkey!
Prerequisites
Summary
There are no semantic tokens being used by the editor. ( I was debugging why semantic colors for the
powershell
language was ignoring all semantic configurations. )It's supposed to look like this:
PowerShell Version
Visual Studio Code Version
Extension Version
Steps to Reproduce
settings.json
*.ps1
file .1 Use token inspector, and you get no info.semantic config
I have every possible semantic config enabled.
Visuals
I think the Language Server is running
This screen shows that these are all running
1 reference
Logs