The matching of inline math is not correctly.

[Edenharder]

this will affect the use of the package preview-inline and cause the problem that Editor is not responding.

From the color of highlighting, we can know that the matching of inline math is not correct. With the package preview-inline installed, moving the cursor into $\nu$ and toggling preview-inline (shortcut ctrl+alt+p) will either give the error that the math is not matching or cause the problem Editor is not responding.

The package preview-inline relies on the matching of math, but I don't know the matching of math is based on the highlighting or not.

[burodepeper]

Could you describe your issue in more detail? What are the exact steps needed to replicate the issue? Can the issue be prevented by disabling the preview-inline package? Have you contacted the author of preview-inline to verify that the issue is not with their package? Etc.

[burodepeper]

I can not seem to replicate your issue. I've tested it in the latest stable version of Atom, and the latest beta. See the attached image.

The color of the highlighting is not as you'd expect it coming from the latest version of language-markdown. Can you verify that you've updated both language-markdown and Atom to their latest versions? And can you export a list of the other packages you have installed? I think there's a conflict with something else that's at the root of this.

If your screenshot comes from a longer document, it is possible that there's something else on the page that causes this conflict. If that is the case, can you post the raw source for me to verify.

[Edenharder]

Thanks for your analysis. As I found, it conflicts with the package language-latex. Is it possible to avoid this? Because language-pfm does not conflict with language-latex.

[burodepeper]

When I enable language-latex, I'm not getting your error either. Are you sure you have language-markdown enabled for your markdown documents?

And can you answer my other questions:

• Can you verify that you've updated both language-markdown and Atom to their latest versions?
• And can you export a list of the other packages you have installed?
• If your screenshot comes from a longer document, it is possible that there's something else on the page that causes this conflict. If that is the case, can you post the raw source for me to verify.

[Edenharder]

• Atom 1.22.1, and all packages are up to date
• The list of installed packages are

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

• The whole contents of the file are $\eta$, $\nu$. If I place the cursor in $\nu$ and try to preview it, I will get the error described above.

[burodepeper]

If you disable all those packages except for language-markdown, language-latex and preview-inline, does the issue still occur?

And another thing you can try, if you open Atom in dev mode, and right click $\eta$, $\nu$ you can select "Inspect Element". This opens the web inspector and shows you the scopes assigned to this element. If you can post a screenshot from that, it will give us an idea of what package might be interfering.

[Edenharder]

The problem is still there, even only language-markdown, language-latex and preview-inline are turned on. Here is the screenshot from "Inspect Element":

[burodepeper]

That is weird. It appears the rules of the grammar are executed in a different order than they are on my machine. I'm going to need to dig into a little deeper when I have more time. You haven't been tinkering with language-markdown in dev-mode at some point, have you?

[Edenharder]

@burodepeper nope, I do not have the ability to do that :P BTW, my operating system is Mac Os 10.11.6.

[burodepeper]

@Edenharder Before I start breaking my head over this, has this issue perhaps resolved itself due to an update of Atom or any of the related packages? In other words, is the issue still relevant? ; )