GHFM: #numbers vs. issue #numbers: How to escape?

[mhulse]

Possibly related to #195.

We all know that an issue can be referenced by: #100 (when not parsed as code).

What do we do when referring to an item in an ordered list (for example)?

Numbers can be escaped …

Not escaped:

1. Seventh.

… escaped:

7. Seventh.

In the latter example, I used a backslash 7\. to turn off the markdown processor.

Other than wrapping them in backticks (like #195), how can type a number (like #195) that doesn't get auto-linked to an existing issue?

Optimally, I'd like to use the \ trick to escape non-issue number numbers (for example):

\#195
… or:
#\195

(Is this right place to file this issue?)

[gjtorikian]

Normally we like issues to come in through github.com/contact. In any case, this most certainly looks like a bug with the Markdown processor. I'll leave this issue open until it's resolved, and in the meantime, file a bug for the right people to look at this. Thanks!

[mhulse]

Thanks for the reply @gjtorikian, I really appreciate it.

Also, thank you for the clarification on where to file issues.

Just to clarify, should I file an issue with RedCarpet issue tracker, or did you mean you'd file the issue for me? Sorry, I just want to make sure I'm helping out as best as I can.

(I know this is a minor issue, but it's been something that's been bugging me for a while … I wasn't sure if I should send it to support@github.com or go directly to the this repo's issue tracker.)

Thanks again!

[gjtorikian]

Ah, you're right, I should've been more specific.

The commit autolink magic is something internal to github.com, so I filed an issue for the team here at GitHub. It's not related to RedCarpet or any other Markdown processor.

Usually support@github.com is best for these sorts of things. But as you can see we're not going to blindly ignore valid quirks that come up, either. 😀

[mhulse]

Got it! Thank you! 👍

[bkeepers]

Thanks for the report. This cant't be fixed by a change to this repository, so I'm going to close this issue. But our internal teams know about this issue.

[rclough]

Is this being tracked anywhere? I use a lot of numbered lists in my GH issues, and then when I refer to them, it's really frustrating to have to type out "choice 1" or similar instead of saying "#1" which then links an irrelevant github issue.

BUT I also really like the feature and use it, so having an escape char makes most sense, IMO.

I tried googling this issue and this is the best link I could find. This has been bothering me for at least a year.

[houtianze]

This cant't be fixed by a change to this repository

Hmm, wondering why so? And is this tracked anywhere? Appreciate it that @bkeepers can give some pointer why this is tracked?

[kivikakk]

One possible workaround is to use a zero-width space (U+200B): #​195. Another is to insert an empty <span>: #195 (#<span></span>195).

Hmm, wondering why so?

The meaning here is that there's no code that's part of the Markup gem which does the issue mention replacement. The issue mention replacement code is part of github's internal stack. (That's why opening issues on github/markup isn't the right place for problems like this.)

[bergus]

Dunno where this can be fixed, but there's a list of workarounds at https://stackoverflow.com/questions/20532546/escape-pound-or-number-sign-in-github-issue-tracker