You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
As an added bonus of painful dark malicious user-defying magic, I had to break the above first link-text into invalidity to get it to display. Below is that same [github/foo]/(github/foo) link expression but with no space between https and :// (which refuses to show the url even though I'm explcitly telling it to), nodejs/node#90 (comment)
Rather than link https ://github.com/iojs/io.js/issues/90#issuecomment-68809524 I wanted to type a short form. I thought nodejs/node#90#issuecomment-68809524 would be worth a logical shot, treating the original expansion term (reference) as something which can be added onto, but it shows up as iojs/io.js#90#issuecomment-68809524.
As an added bonus of painful dark malicious user-defying magic, I had to break the above first link-text into invalidity to get it to display. Below is that same [github/foo]/(github/foo) link expression but with no space between https and :// (which refuses to show the url even though I'm explcitly telling it to),
nodejs/node#90 (comment)
One additional test case for URL-expansions:
nodejs/node#90?foo
The text was updated successfully, but these errors were encountered: