It's almost certain that the poster didn't hit preview at all.
It might be worthwhile to think about some kind of heuristic
for posts where if they look 'codish' enough, the submit button is rewired to preview, initially. The presence of
symbols meaningful to perl ($@%), combined with semicolons
near newlines might be good enough to catch most cases of
this. | [reply] |
Looking at SamueD2 I see it says Writeups: 15 , which warrants a "/msg" and/or a --, especially
since unless you go to User Settings, and turn on the "No Forced Preview" setting, you will be forced to preview.
I really see no reason for editors to go around adding <CODE> tags to posts of users who've been around long enough to know better.
As for caring, by the time I read the post the formatting was fixed, and the question still not answered.
Looking at the previous questions asked by SamueD2 I can see that he's still working on his database problem.
I personally don't care to read or answer any more questions by SamueD2, but I'm feeling a little grumpy.
I did -- him for being lazy.
If you want help, be nice and format your posts properly, it's the least you could do. | [reply]
[d/l] |