There are some subtle rules for editing root nodes. I confess I haven't found all of them, references can be found in How do I change/delete my post?, Changeing a Frontpage Node, and various other places. If you're really curious, use Super Search.

It may help to reread the nodes listed in Perl Monks Site FAQ, which describe (among other things) the markup tags you can include in your posts to make them easier to read and where you should direct your questions.

Also, you can use the CB to experiment with linking techniques by /msg-ing yourself.

Finally, there are a number of nodes containing excellent advice for posting well-crafted (or at least legible) posts. Start with Before You Post ... and use Search to find other related posts.

--f

P.S. I've found it helpful to make careful use of the Preview button. It's cut down on the number of markup errors in my posts, even if it means I spend more time editing the post than composing it. (Most times I find myself doing that, I cancel the post. If I'm having that much problem expressing my thoughts, well, it usually means I should consider my petition a little longer.)

I posted over 40 nodes, and used a lot of formatting and linking. Actually, I wrote the readonly node in an editor, to prevent mistakes and so on. It contained numerous P-tags as well as I- and at least 4 separate code-sections.

They just happened to be completely ignored when posting. Worse, everything was there in preview state, but not when submitted. And my worries were not over.

Because (Hey, this guy knows more HTML-tags!)

I was not able to change my nodes!!!!

If you still don't believe me, look at my homenode. Readonly is nicely formatted there. See? BTW, the original Readonly error on $_ is now formatted OK as well. Thanks to some magic from vroom, I suppose.

Jeroen, who nearly starts to wish he wasn't begun with that question at all.
I was dreaming of guitarnotes that would irritate an executive kind of guy (FZ)

<code>
  put your code here
[download]

According to jereones in chatter he did use code tags. His repost was at my request and I specifically told him to use code tags. So it is fairly certainly not ignorance of code tags that caused his formatting problem.

Thank you for the context tilly.
Perhaps I didn't completely understand the question. :-(

However, before I posted my response, I looked at the HTML source of the post mentioned in his question (which upon inspection was just as ugly as he said), and found no TT PRE or CODE tags. So, I tried to do my homework.
mkmcconn
html " programmer "
perl wannabe