-
Notifications
You must be signed in to change notification settings - Fork 49
multiple issues detecting documentation keywords #136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I want to point out that the project file, 'build.ps1' contains malformed help documentation. These both cause Get-Help to not display any of the comment help. |
This will be the one of the next items I'll contribute a PR for. |
msftrncs
added a commit
to msftrncs/EditorSyntax
that referenced
this issue
May 11, 2019
optimize single line comment use \G in and optimize commentEmbeddedDocs matches
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Issue Description
Presently, the documentation keyword detection/scoping/theming fails on the following items:
# .keyword
doesn't detect and scope<# .keyword
doesn't detect and scope#
separated by spaces allows the keyword to detect, but Get-Help doesn't seem to permit this.Screenshots
(Showing modified sample from file attached to #134)
Expected Behavior
Expected to match Get-Help's acceptance. However, that's much more difficult. Get-Help also accepts:
<#
#>
#
<additional#
s>.keyword
.keyword
if the containing comment doesn't otherwise start at the beginning of a linePossible Fix
I think two changes could fix the easiest problems.
(#\1 match)
and change the capture from "0" to "1".
With the changes applied, this is the result:
(not necessary valid, I know)
The text was updated successfully, but these errors were encountered: