-
Notifications
You must be signed in to change notification settings - Fork 167
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
Spurious bold/italic in inline code #172
Comments
Two of the three are still failing, but one has been fixed. Thanks to Kévin Le Gouguec (GH-172).
Thank you. I have added these test cases (although I screwed them up the first time) and am working on a fix. I'm not sure which way best, but previously in such cases I used |
I think these should be fixed now, but please let me know if not. |
As far as I can tell, these bugs are now fixed. Thanks a lot! I just have a comment about one of the tests: while fixing I watched the commit log this past month and I have to say, the amount of work you have put on markdown-mode is incredible! Thank you for working so hard on this package. Clickable links, code block fontification/edition are wonderful quality-of-life improvements; I played around with markup-hiding and even though I do not see myself using it all that much, it does look very polished! |
Thanks for spotting that! I was fixing several problems related to italics last night and that slipped through. It shouldn't be italic or bold, so I updated the test to check the absence of both. I'm glad you like the recent changes. I'm glad to be able to give the package some needed attention lately! |
Hi! I have noticed that in blocks such as headers or blockquotes,
inline code containing bold/italic markers will behave as if the
inline code markers were not here. IOW text between asterisks or
underscores will be shown as bold/italic.
Some test cases I wrote:
(Not sure that
(should-error (markdown-test-range-has-face …))
isthe most idiomatic way to test this, though I do mean to check the
absence of bold/italic fontification)
I tried poking around in the code, but I could not pinpoint the cause
of the issue. Some things I noticed, which may or may not be related:
(markdown-match-bold (point-at-eol))
will match these strings whenthe point is at the beginning of each line:
In similar conditions,
(markdown-match-code (point-at-eol))
failsto match, though
(markdown-match-code (point-max))
does match:That's all I have for now.
The text was updated successfully, but these errors were encountered: