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

Workaround invasive use of tex mode inside of code elements and blocks #10867

Merged

Conversation

krassowski
Copy link
Member

References

Fixes #6774

Code changes

Prevent multiplexing mode from applying tex mode inside of code blocks by re-delegating parsing in those instances back to gfmMode parser.

User-facing changes

before after
Screenshot from 2021-08-18 14-28-10 Screenshot from 2021-08-18 14-28-32
Screenshot from 2021-08-18 14-24-45 Screenshot from 2021-08-18 14-33-34
Screenshot from 2021-08-18 14-20-25 Screenshot from 2021-08-18 14-20-42
Screenshot from 2021-08-18 14-20-31 Screenshot from 2021-08-18 14-20-50

Backwards-incompatible changes

None

@jupyterlab-dev-mode
Copy link

Thanks for making a pull request to JupyterLab!

To try out this branch on binder, follow this link: Binder

Copy link
Member

@goanpeca goanpeca left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@krassowski krassowski marked this pull request as draft August 18, 2021 15:53
@krassowski krassowski marked this pull request as ready for review August 18, 2021 17:28
@krassowski
Copy link
Member Author

I added two visual tests, one for latex highlighting and one for the bug being fixed:

image

image

@krassowski krassowski added this to the 3.1.x milestone Aug 19, 2021
@krassowski krassowski added the bug label Aug 19, 2021
@fperez
Copy link
Contributor

fperez commented Aug 24, 2021

Thx so much @krassowski for this! Big, big improvement to something that's been nagging many of us for a while. Much appreciated!

I'm far from an expert in the Codemirror TS code, but from a quick look at the changes, given how limited in scope they are, this looks very good - the actual functional changes are tight and simple, and most of the new code in the PR is tests and examples. So from a semi-outsider view, this looks solid, thanks again!

@blink1073 blink1073 merged commit b6e0be1 into jupyterlab:master Aug 24, 2021
@blink1073
Copy link
Contributor

@meeseeksdev please backport to 3.1.x

meeseeksmachine pushed a commit to meeseeksmachine/jupyterlab that referenced this pull request Aug 24, 2021
blink1073 pushed a commit that referenced this pull request Aug 24, 2021
…e elements and blocks (#10901)

Co-authored-by: Michał Krassowski <5832902+krassowski@users.noreply.github.com>
@github-actions github-actions bot added the status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Feb 21, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug pkg:codemirror status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. tag:Testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Markdown syntax highlighting bug due to a dollar sign ($) within a code block
4 participants