7
votes
Possible bug: using the ~ character preceding a word within inline preformatted text.
In preformatted text blocks (three back ticks), group syntax with ~ doesn't get rendered as a hyperlink, but it does with inline preformatted text e.g. ~group.
This seems like it would be undesirable and unintended behavior. That being said, I'd rather have this verified before opening an issue on gitlab.
Is this a bug or a feature?
We haven't decided yet, LOL. I suspect this was just a quick and dirty fix for an issue pointed out a few days ago where inline code links didn't show as blue or underlined despite being clickable. I personally think allowing links within inline code segments is useful for quoting people... but I also think we need to implement a way to escape them as well.
E.g.
\~tildesshould prevent the group link from forming and not show the\, especially for things not meant to be tildes group references.@deimos will have to comment on the feasibility of all this parsing though since inline code is tricky and sometimes
\~somethingmight need to show up exactly as written with the\ahead of it... but in which case\\might be required to accomplish that. Like I said, it gets complicated. :PBoth funny and kind of profound at the same time, now I really wish we had that save comment feature :D
I agree that at the very least, escaping is a necessity. Especially for any programming-related submissions, using
~as the logical NOT operator could prove problematic and require going back in and adding additional spacing, and there are likely other cases e.g. plaintext for strings that shouldn't be clickable.