Given that Markdown has lots of undefined semantics, this may very well be a valid interpretation of certain broken Markdown documents. But I guess most would agree that the priority should be the other way around.
Example: (Save as `something.md` and open with Geany)
_This is "underlined"
``` should_be code ```
This sentence is considered code, because the "matching" underscores had priority (?)
Note that the "stray underline" can also occur in HTML inline-comments, where they don't stand for underlining anyway.
<!-- Like this one. I know very well that this won't usually appear. -->
Yes well, markdown is only defined by the processor you use, "no the one I use", "no the other one"...
[full disclosure, as an Asciidoc maintainer I am required to diss Markdown at every opportunity :wink: ]
The Markdown lexer is part of the editing component we use, Scintilla.
Can you describe what "rule" you suggest to decide that the underscore is not going to be matched and propose it to the [Scintilla project](https://sourceforge.net/p/scintilla/bugs/) if it isn't already listed.
[Reported upstream,](https://sourceforge.net/p/scintilla/bugs/1216/) but I'm not too optimistic about it getting any attention.
Patched in a forthcoming release of `lexilla`: https://github.com/ScintillaOrg/lexilla/commit/ca976aaa2d505e5d7fe5f11a2d7be...
![Screenshot_2021-06-28_20-40-13](https://user-images.githubusercontent.com/59004801/123720187-80377200-d851-1...)
![Screenshot_2021-06-28_20-41-48](https://user-images.githubusercontent.com/59004801/123720203-888fad00-d851-1...)
:warning: For "forthcoming" read "_after_ v5.1.1", to avoid one nasty bug: https://github.com/ScintillaOrg/lexilla/issues/23 :warning:
Closed #1439 as completed.
Since we already use Scintilla 5.1.5 where this bug is fixed, I'll close this issue.
Just re-open if you disagree.
github-comments@lists.geany.org