[Markdown] Respect all whitespace characters #110515
Unanswered
James-E-A
asked this question in
Projects and Issues
Replies: 1 comment 2 replies
-
Thanks for posting in the GitHub Community, @JamesTheAwesomeDude ! We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Projects and Issues category is solely related to conversations around the GitHub products Issues and Projects. I've gone ahead and moved it for you. Good luck! |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Product Feedback
Feature Area
Issues
Body
I wish that the Markdown parser you use had better whitespace detection, particularly when it comes to auto-linkifying commits.
Current Behavior (undesirable)
For example, if I type the following fragment:
It renders as:
This is a bummer because it doesn't link the issue, which is a major lack of functionality.
Current workaround #1 (undesirable)
If I stick a space after “pre-”, it works:
But this is a bummer because it's pretty hideous.
Current workaround #2 (undesirable)
If I manually format it, it works:
This is a bummer because it's extra work.
Requested workaround
The Zero-Width Non-Joiner character was made for this use-case, where you want two semantically- and whitespace-separated "words" to be displayed physically "without" any whitespace between them, even though the whitespace logically exists:
Another alternative fix would be to revert the /IMPLIB injection code to its pre-‌06830ada1cda3595d2a1f222fd8cbed35bdb691e behavior, just nestling it in a top-level …
but Github doesn't currently respect this, rendering the HTML exactly as if there were no whitespace characters surrounding the commit hash.
(I seem to be the first to ask this.)
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions