Skip to content

Conversation

@JohnRoos
Copy link
Contributor

Since my last PR I thought I would go ahead and fix the rest of the issues I have found with the PowerShell lexer.

This PR contains some pretty big improvements to the PowerShell lexer. I have tested it with a lot of the built in themes to make sure no strange behaviour occurs and it looks good.

Most themes don't have support for all the token types so they don't show the full potential. I am using Hugo with a theme I have created myself which basically looks like VSCode and it looks very good.

Please let me know if you would like me to add or change anything.

{"type":"Text","value":" "},
{"type":"Punctuation","value":"*."},
{"type":"Name","value":"txt"},
{"type":"Text","value":"\n\n"},
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be TextWhitespace?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very minor nit and won't make any difference, so I merged it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might do more improvements a bit later, so I can look into this next time

@alecthomas alecthomas merged commit f07788e into alecthomas:master Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants