fix: Update newline matching in lexer to support both LF and CRLF#56
Merged
Yang-Emily merged 3 commits intomainfrom Sep 17, 2025
Merged
Conversation
added 2 commits
August 23, 2025 20:40
This was referenced Aug 23, 2025
Silvan-M
deleted the
18-parse-error-when-changing-a-number-in-an-example
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix of #18
Apparently the parser was missing a definition to catch carriage return characters which are generated on windows upon changing something in the editor, which caused a parse error.
Thanks to @azable to figuring this out!
Notes:
pageandshow <obj>command if not already present as described as part of Autocomplete matrix example doesn't always work #58