You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently the semantic highlighting assumes your editor already does the basic syntax highlighting, but vscode's sucks because it uses an abandoned 3rd party package (microsoft/pylance-release#5824)
this would address all issues labelled with
vscode syntax highlightingissues with vscode's native python syntax highlighting rather than an issue with our LSP
, along with this neovim syntax highlighting issue with match statements that was raised in the discord:
probably also need to figure out #147, as there are two different colours used (in vscode at least) for keywords and i'm not sure what the distinction between them is supposed to be
The text was updated successfully, but these errors were encountered:
currently the semantic highlighting assumes your editor already does the basic syntax highlighting, but vscode's sucks because it uses an abandoned 3rd party package (microsoft/pylance-release#5824)
this would address all issues labelled with vscode syntax highlightingissues with vscode's native python syntax highlighting rather than an issue with our LSP
, along with this neovim syntax highlighting issue with
match
statements that was raised in the discord:probably also need to figure out #147, as there are two different colours used (in vscode at least) for keywords and i'm not sure what the distinction between them is supposed to be
The text was updated successfully, but these errors were encountered: