Skip to content
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

Broken markdown highlighting after 1.92.0 upgrade #224627

Closed
memeplex opened this issue Aug 2, 2024 · 2 comments
Closed

Broken markdown highlighting after 1.92.0 upgrade #224627

memeplex opened this issue Aug 2, 2024 · 2 comments
Assignees
Labels
*caused-by-extension Issue identified to be caused by an extension

Comments

@memeplex
Copy link

memeplex commented Aug 2, 2024

Does this issue occur when all extensions are disabled?: I'm reporting a conflict with an extension, so I left that one enabled.

  • VS Code Version: 1.92.0
  • OS Version: macOS Sonoma 14.4.1

After upgrading to 1.92.0 syntax highlighting for qmd files (Quarto extension) started showing the same issues that were described some days ago wrt the builtin markdown support. That issue was marked as duplicate (it's not clear to me that it's a duplicate) and then closed by a bot as not planned. I don't know if this is a regression in VSCode or an issue that should be addressed by the extension, but it's clearly something going on that's related to a change in latest release.


@mjbvz
Copy link
Collaborator

mjbvz commented Aug 2, 2024

Please Marking as caused by extension. Sounds like they may need to update their grammar based on changes to our markdown grammar

They can follow up here if there really a problem on the VS Code side

@mjbvz mjbvz closed this as completed Aug 2, 2024
@mjbvz mjbvz added the *caused-by-extension Issue identified to be caused by an extension label Aug 2, 2024
@memeplex
Copy link
Author

memeplex commented Aug 2, 2024

Ok @mjbvz thanks for the clarification.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*caused-by-extension Issue identified to be caused by an extension
Projects
None yet
Development

No branches or pull requests

2 participants