Useless Edit history
-
Continuing the discussion from From a single INSERT statement:
I'm betting he confused
#tempArrayTable
and##tempArrayTable
. The two behave enough different that the check is necessary with the double hash, but not the single hash. I actually had to teach my boss (the DBA/CIO) the distinction between the two.I got a notification that @boomzilla edited one of my posts, and saw that he fixed the quote so that it works. Nice! Take a look at the history to see what he did:
Well, baked history doesn't show anything, let's take a look at the raw:
Hmmm ...
I'm going with rebake.
-
No, I added those newlines. The diff just can't handle that. Seen it before...last time on..umm....@ijij's post.
-
No, I added those newlines. The diff just can't handle that. Seen it before...last time on..umm....@ijij's post.
In that case: Why does nesting a code block in a quote require those newlines? The raw of this post has no newlines in the quote, and it works fine.
INB4: [Discourse sucks], [Discoparsing]
-
Why does nesting a code block in a quote require those newlines?
Yeah....newlines are always the answer. Like rebooting a Windows machine.
-
Went to report on meta.d, but they appear to be down.
-
And back up. Here we go:
Yes, most of that is copied from the Discoparsing definition. Why do you ask? ;)
-
Why does nesting a code block in a quote require those newlines?
Because <abbr title="The Penishorse implementation of BBCode.
Maybe even the concept of BBCode itself. Who knows, I've mostly used it here, and it's awful here.
(On a related note, check the raw for this and despair...)">DicsoBBQWTFCode sucks dog eggs.
-
Preview is the thing at the top with the matrix text, editor is below that.In other words, the Discoimplementation of BBCode itself is already broken:
[code]
teh codez
[/code]