-
Notifications
You must be signed in to change notification settings - Fork 163
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
Invalid matching of emphasize in html #410
Comments
Thanks for reporting issue. I have merged PR #441. Please check latest version. |
Does the PR #441 also address code spans like this?
|
No However is there any use case with such attribute value(starts with backtick)? |
Maybe this:
|
It looks backticks are not in HTML tag attribute field. |
Shohei YOSHIDA hat am Mo 13. Apr, 05:59 (-0700) geschrieben:
It looks backticks are not in HTML tag attribute field.
Yes, but they are in an HTML block and become highlighted, while they
don't match a Markdown element. This becomes annoying if they span
multiple lines.
<head>
<title>This is about backticks `</title>
<meta name="twitter:site" content="@jo_so7">
<meta name="twitter:creator" content="@jo_so7">
<meta name="twitter:domain" content="alea.gnuu.de">
<meta name="og:title" content="This is about backticks `" />
</head>
…
-- You are receiving this because you authored the thread. Reply to this
email directly or view it on GitHub:
#410 (comment)
|
I see however I suppose fixing that issue is very difficult with current implementation. I suppose you can use decimal/hexadecimal reference like |
Expected Behavior
In HTML blocks no matching of
*
,_
or`
should happen.Actual Behavior
In
the
twitter:creator
and all around becomes highlighted as emphasized.Steps to Reproduce
emacs -Q --load path/to/markdown-mode.el /tmp/test.md
twitter:creator
C-u C-x =
face (markdown-html-attr-name-face markdown-italic-face)
containsitalic
Software Versions
2.4-dev
GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.10) of 2019-07-22, modified by Debian
The text was updated successfully, but these errors were encountered: