Thanks for feedback! =)

regarding code sections:

Problem is that JS has no lookbehind assertion for regex.

In order to keep it simple and compatible I'm grabbing the surrounding white spaces too.

If you separate your code by more then one whitespace it works again.

'one'  'two'  'three'

one two three

please note how HTML ignores multiple whitespace.

(This is a very contrived example anyway don't you think? ;)

I could solve this with at least one look ahead assertion, though I'm not sure about incompatibilities. (on todo list now)

Please keep in mind that you can still use the old and consistent markup.

The wiki stuff is more a mix of DWIM and Huffman coding, not a complete replacement. =)

Yes I was thinking about this, but than we need a new mark up for doc links

 ?print? print

Suggestions?

update

But please be aware that the problem with look around assertions strikes here again.

I have no problem with coding this, but testing would be a pain. ..

I think # is faster to type but question mark is definitively more related to documentation. I'd go for it.

PS sorry i'v a bit misunderstood (question mark yet used for doclinks). # as for comments? or = as for POD?

Also a comprensive cheetsheet will be useful at the end of your OP

L*

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

> Also a comprensive cheetsheet will be useful at the end of your OP

ehm ... what's wrong with the demo sections in

• Good Intentions: Wikisyntax for the Monastery and
• Re: Good Intentions: Wikisyntax for the Monastery (New Features)
?

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!}