I do have a theory actually why that happened, probably the limit for finding the matching closing symbol/tag in the post body is less than the size of it for the parser that tries to find the matching tags, so it thinks it must not be a code block since it gives up before it reads all the 65535 characters, and since I wanted the first and last character to be code in a 65535 character post that did not work because of that. alternatively it interprets one of those symbols alone on a line as not itself, or something else like that, I will give another experiment a go later today to see if adding characters after and before the symbols helps and maybe try to explore how far they reach, but it would be easier to look at the parser code if it was available, could maybe tell then what is going on, but my coding is very rusty and I have been far too annoying about this already, sorry.
`
mini test no text near the ticks ‘does it work?’ “do I still have straight quotes?” … — at least the editor looks right, let’s see post though…
`
no that broke ok let’s try one with text right after and before the code things
`//this is code you silly parser
mini test no text near the ticks ‘does it work?’ “do I still have straight quotes?” … — at least the editor looks right, let’s see post though…
//this is code you silly parser`
hmm no ok…
switching on rich text thingy and selecting text this time:
"I continue to fight and fight the 'horrors' of the parser, ... let me be free" let me continue to add more code please yes ok this looks good in the editor 'will it remain good when I save changes'? still parses ... on typing them in side of code --- and the dashes too, it should not be doing that, but that is fine I can perhaps force it to work, does it though 'yes' or "no" :) no smileys I like them as text (:
now switching off rich text in edit, does it break that code block?
no it did not for some reason how can it tell the difference is it an empty line that wrecks it?
`“I continue to fight and fight the ‘horrors’ of the parser, … let me be free” let me continue to add more code please yes ok this looks good in the editor ‘will it remain good when I save changes’? still parses
empty lines
… on typing them in side of code — and the dashes too, it should not be doing that, but that is fine I can perhaps force it to work, does it though ‘yes’ or “no” 🙂 no smileys I like them as text (:`
yes that broke it let’s see if one new line breaks it
"I continue to fight and fight the 'horrors' of the parser, ... let me be free" let me continue to add more code please yes ok this looks good in the editor 'will it remain good when I save changes'? still parses
... on typing them in side of code --- and the dashes too, it should not be doing that, but that is fine I can perhaps force it to work, does it though 'yes' or "no" :) no smileys I like them as text (:
one new line is okay what about two
`“I continue to fight and fight the ‘horrors’ of the parser, … let me be free” let me continue to add more code please yes ok this looks good in the editor ‘will it remain good when I save changes’? still parses
… on typing them in side of code — and the dashes too, it should not be doing that, but that is fine I can perhaps force it to work, does it though ‘yes’ or “no” 🙂 no smileys I like them as text (:`
two new lines like is normal in any code programmers will write and quote breaks the code block, figured it out 🙂