NoTypeInformation Incorrectly Colored #23

Activity

1. guillermooo

   added

   T:bug

   syntax

   on Oct 10, 2014
2. vors commented on Dec 6, 2014

   

   vors

   on Dec 6, 2014

   Member

   More actions

   This problem shows up on other keyword-prefixes (like -bxor)
   I investigated it and there is a simple fix: add \b for word boundary

   https://github.com/SublimeText/PowerShell/blob/dev/Support/PowershellSyntax.tmLanguage#L265

   -           <string>-(?i:and|or|not|xor)|!</string>
   +           <string>-(?i:and|or|not|xor)\b|!</string>

   The tricky part that it's not a 100% accurate fix. In PS it's legal to write -not1 and 1-bxor1, without spaces.

   A proper fix will be relatively complicated: we need to recognize that context implies function call and turn-off keyword highlighting for all -bla keywords. It's pretty easy to introduce new bugs, when implementing this, so I would prefer implement it with reasonable test coverage.

   @guillermooo what do you think?

   PS: -not1 ideally should be recognized correctly (highlight -not part), but I have no idea how to do it without using PS parser or over-engineering.
3. bcrotty commented on Feb 18, 2015

   

   bcrotty

   on Feb 18, 2015

   ContributorAuthor

   More actions

   Fixed as of 2.1.0
4. bcrotty

   closed this as completedon Feb 18, 2015
5. michaelblyons

   added the

   Bug

   issue type on Dec 9, 2025
6. michaelblyons

   removed

   T:Bug

   on Dec 9, 2025