*(**foo** bar)* ignores bolding
-
*(**foo** bar)* ignores bolding
(foo bar) ignores bolding
*(****foo**** bar)* respects bolding
(foo bar) respects bolding
-
I think it doesn't ignore bolding per se.
*(**foo** bar)*
111222223333333
It just treats
**
as if it was}{
, or[/i][i]
. I guess treating consecutive**
exclusively as bold tags shouldn't break too many things, but hell if I know...
-
_(**foo** bar)_
(foo bar)
*(__foo__ bar)*
(foo bar)
-
Escape the * with a .
-
You mean with a \. You just escaped your
.
for some reason.
-
for some reason.
I did not expect periods to be escapable. I'm not typing a regular expression.
-
Ah. the joys of
Discoursdiscussing escaping multiple input formats.On a forum that supports multiple input formats.
Simultaneously.
-
Now that I poke at it, the escaping is really broken.
This:
\<hr>
Renders:
<hr>
Why the hell would that render a horizontal rule!?
-
Is that a vase or is it two faces?}{
-
Yes.
-
-
-
Because the < should be escaped?
-
So the answer to riking's "why the hell?" question would be, "Because the less-than sign isn't being escaped."
-
Yes.
Have I just been part of a socratic dialogue?
-
Why the hell would that render a horizontal rule!?
Use < to escape <. From experimentation while writing one of my pinned topics, I found that 's escaping (and escaping in general) is somewhat spotty and hit-and-miss...
-
I found that 's escaping (and escaping in general) is somewhat spotty and hit-and-miss...
Yes. I think markdown (or Discourse's implementation of it; I'm not sure who is at fault) took Emerson's statement "consistency is the hobgoblin of little minds" way too much to heart, failing to notice that he said "foolish consistency," and just threw all consistency into the rubbish.
-
I did not expect periods to be escapable. I'm not typing a regular expression.
This is vim-inspired, remember? (j/k shortcuts) You need to escape the period to be interpreted as a regex wildcard unlike every other regex interpreter ever.
Wait... this made no sense. None of this makes sense. AAAH!
Filed under: I use way too many editors
-
Use < to escape <. From experimentation while writing one of my pinned topics, I found that 's escaping (and escaping in general) is somewhat spotty and hit-and-miss...
I, for one, would not expect a backslash to escape a less than symbol in a web environment.
-
-
So when quoting
...your quote contains the rendered text, not the text required to render that text.
Yes. This has been raised before.
If you want the text required to render (which should have been supplied to begin with), you need to go look at the raw post and copy/paste manually from there.
-
Minor Markdown annoyance:
***imperfectly-matched** emphasis*
doesn't get parsed, so we have to use***extra*** *markup*
since whitespace apparently* **doesn't** help*
...Actually, i just noticed:
*that **inner bold** doesn't work within italics*
. WTF?! Maybe this might be accepted for SO since it's about code and Q&A, but for a goddamn FORUM?!?
-
Hmm, that is odd.
*this is italic **with some bold** inside*
this is italic with some bold inside
_this is italic **with some bold** inside_
this is italic with some bold inside
Consensus on Babelmark is that it should work, so it's a bug in https://github.com/evilstreak/markdown-js
@eviltrout this should be on your list since it's kind of egregious, and works in most other Markdown implementations..
-
I've got a fix in master for this:
-