I just noticed that <pre> tags allowed that <p> tags were included which is against the meaning of "pre-formatting".

pre-blocks are now excluded from any wiki-expansion

<pre>
*a* /b/
# 2 newlines following

https://perlmonks.org/
</pre>
[download]

displays now as

*a* /b/
# 2 newlines following

https://perlmonks.org/

update

<blockquote> are now also excluded, but that's experimental.

Why should pre tags be handled like code tags? °

AFAIR do pre tags never block any other expansion, I wouldn't know why they should.

Could you please elaborate?

Edit:

Please think about how

<pre>a
<code>bla</code>
b</pre>
[download]

is rendered

a
bla
b

update Feb 07 2020

°) OK paragraph is a reason, see Re^2: Good Intentions: Wikisyntax for the Monastery (pre-blocks excluded now)

I have only to find a way to make nowiki invisible in output but persistent in edit mode.

  <nowiki>  <pre> 

perl -we 'say' 

</pre> </nowiki>
[download]

<nowiki>

 

perl -we 'say' 

Wrap it in <!-- ... -->?

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
[download]

Yes it's possible, but it breaks the orthogonal approach how I combine features.

I have to think about the best maintainable way in this "framework".

for instance what has priority when parsing? <c> or <nowiki> ?

And more importantly, would you use <nowiki> ?

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