regex issue in parsing TLC output
See original GitHub issueHello, the output of my model checking has lines like the following
<Write1 line 20, col 1 to line 20, col 6 of module spec (21 5 22 20)>: 6:27
which are not parsed by the regex https://github.com/alygin/vscode-tlaplus/blob/031ad983023cea0bc5fba2a1a54f835fed2cfd04/src/parsers/tlc.ts#L467
and they don’t show up in the coverage section of the output panel.
I think the values unexpected in the regex are (21 5 22 20)
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Using regexp to parse data - The Tcl programming language
I am trying to use regexp when parsing a data file. ... comma on the end of the regular expression which isn't in...
Read more >Defining a Regular Expression for a Normalization Rule
If the expression is valid, TLC presents the output in the Test Output field. If no output is returned, the Test History tab...
Read more >TCL Regex ignore/parse leading asterisks in string
I am not in a position to change the error output, so I must change the regex parsing to either ignore the "***"...
Read more >Regular Expression Examples - the Tcler's Wiki!
Regular Expression Examples is a list, roughly sorted by complexity, of regular expression examples. It also serves as both a library of useful...
Read more >Solved: RegEx issue with string - Designer - Alteryx Community
My expected output is the number after "XYZ.", so I wanted to parse the digits after XYZ. and exclude the bracket (]) behind....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The fix is available in the v1.6.0-alpha.2 pre-release.
@giacomociti, thanks for the report!