question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

New syntax coloring doesn't work correctly (preview)

See original GitHub issue

Issue Description

I am experiencing a problem with… coloring syntax.

I know Monokai is not yet working properly (I saw a PR fix for this) but it was showing more or less consistently. But now I noticed that something is weird

image

Describe 'Select-Properties' {
    It 'Select-Properties - Testing Array of PSCustomObjects' {

        $Object1 = [PSCustomobject] @{
            Name1 = '1'
            Name2 = '3'
            Name3 = '5'
        }
        $Object2 = [PSCustomobject] @{
            Name4 = '2'
            Name5 = '6'
            Name6 = '7'
        }

        Select-Properties -Objects $Object1, $Object2 -AllProperties | Should -Be Name1, Name2, Name3, Name4, Name5, Name6
        $Object1, $Object2 | Select-Properties -AllProperties | Should -Be Name1, Name2, Name3, Name4, Name5, Name6
        $Object1, $Object2 | Select-Properties -AllProperties -ExcludeProperty Name6 -Property Name3 | Should -Be Name3

    }
    It 'Select-Properties - Testing Array of OrderedDictionary' {
        $Object3 = [Ordered] @{
            Name1 = '1'
            Name2 = '3'
            Name3 = '5'
        }
        $Object4 = [Ordered] @{
            Name4 = '2'
            Name5 = '6'
            Name6 = '7'
        }

        Select-Properties -Objects $Object3, $Object4 -AllProperties | Should -Be Name1, Name2, Name3, Name4, Name5, Name6
        $Object3, $Object4 | Select-Properties -AllProperties | Should -Be Name1, Name2, Name3, Name4, Name5, Name6
    }
}

I can continue adding new lines:

image

image

And it seems like it stopped working. Restarting PS session fixes this issue.

Attached Logs

1596304553-9b1c68c9-c15f-43c6-9739-e1b537cd361b1596304549455.zip

Environment Information

Visual Studio Code

Name Version
Operating System Windows_NT x64 10.0.19041
VSCode 1.47.3
PowerShell Extension Version 2020.7.0

PowerShell Information

Name Value
PSVersion 5.1.19041.1
PSEdition Desktop
PSCompatibleVersions 1.0 2.0 3.0 4.0 5.0 5.1.19041.1
BuildVersion 10.0.19041.1
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Visual Studio Code Extensions

Visual Studio Code Extensions(Click to Expand)
Extension Author Version
bracket-pair-colorizer-2 CoenraadS 0.2.0
code-settings-sync Shan 3.4.3
github-linker gimenete 0.2.3
gitlens eamodio 10.2.2
markdown-all-in-one yzhang 3.2.0
material-icon-theme PKief 4.2.0
powershell-preview ms-vscode 2020.7.0
project-manager alefragnani 11.1.0
run-in-powershell tobysmith568 1.0.1
vscode-markdownlint DavidAnson 0.36.2
vscode-pull-request-github GitHub 0.18.0
vscode-toggle-quotes BriteSnow 0.3.3
vscode-wakatime WakaTime 4.0.0
vscode-yaml redhat 0.9.1
xml DotJoshJohnson 2.5.1

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:14 (11 by maintainers)

github_iconTop GitHub Comments

1reaction
andschwacommented, Aug 19, 2021

I know the bot closed this automatically, but I wanted to add that we intentionally disabled semantic highlighting by default a while back in #3377 because it was too buggy. Eventually when the rest of the backlog is cleared out I plan to work on stabilizing that feature and re-releasing it with proper test coverage.

1reaction
PrzemyslawKlyscommented, Sep 16, 2020

I believe that’s what @rjmholt is doing right now, and a reason why we didn’t see new releases for a while now. That they are working on making it more robust. I guess it’s so much you can do in current implementation that they need to rewrite huge portions of it, in which case things take time. I feel your pain every day and I restart PowerShell instance every X minutes because something stops working.

Right now intellisense stops working, highlighting stops working, types completion stops working but there’s not much I can do.

Read more comments on GitHub >

github_iconTop Results From Across the Web

C++ syntax coloring not working for CMake project
With that change I don't see any syntax coloring issues. So as stated above, the cl.exe command line parser does it correct and...
Read more >
syntax highlighting broken in xcode 11? - Apple Developer
Yes, syntax highlighting is badly broken in Xcode 11. Randomly code is not or wrongly highlighted. It does not help you but it...
Read more >
Syntax coloring not working. · Issue #111 · microsoft/vscode ...
guys i found a solution to fix this. Open your VS code and press the settings icon at the bottom left. Then come...
Read more >
Why does syntax highlighting only work when previewing an ...
I suspect that C# is an alias for the csharp Markdown content, and the aliasing isn't working properly or something.
Read more >
Advanced syntax coloring not working properly in 'Show Diff ...
Advanced syntax coloring not working properly in 'Show Diff' window · 1. Make a change in any file · 2. Choose in menu...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found