-
Notifications
You must be signed in to change notification settings - Fork 143
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
Markdown syntax test failure investigation #62
Comments
Interesting. I remember running into the problem where Sublime would avoid following infinite push/pop cycles. I implemented that I think by keeping track of a set of contexts already attempted at a position, but it seems Sublime just implemented it by saying "if you push and then pop at the same position, it must be a cycle". |
Yeah ST's method was lazy ;) no idea what their new implementation will be though. Anyway, my PR to the ST Default Packages repo with a fix for this has been merged, so we could choose to update https://github.com/trishume/Packages also :) |
This is now passing all tests:
|
Although the Markdown syntax tests pass on Sublime Text build 3126, it is currently failing in
syntect
becausesyntect
doesn't suffer from this bug: sublimehq/sublime_text#1190Therefore, in
syntect
, https://github.com/trishume/Packages/blob/537d1bfa5bc205aa461b12eb3c996935e017e575/Markdown/Markdown.sublime-syntax#L758 is popping immediately after the push. As it is not a bug insyntect
, and the aforementioned bug will be fixed in the next ST build, it can definitely be considered a bug in the syntax definition, which will need a tweak to continue working as expected.The test line in question is:
The text was updated successfully, but these errors were encountered: