[pmwiki-users] Modified (:markup:)

chr at home.se chr at home.se
Sun Mar 20 08:05:21 CST 2005


On Sat, 19 Mar 2005, Patrick R. Michaud wrote:

> On Sat, Mar 19, 2005 at 09:49:07PM -0600, Patrick R. Michaud wrote:
> > On Sat, Mar 19, 2005 at 09:12:43PM -0500, Neil Herber wrote:
> > > 
> > > This is a great improvement, but (:markup:) gets fooled by enclosed "[=" . 
> > > Perhaps the [=..=] parsing beats out the (:markup:) ... (:markupend:) 
> > > parsing.
> > 
> > Oh, darnit.  (:markup:) gets fooled if the first non-whitespace thing 
> > it encounters is a [=...=].  I'll try switching the order.
> 
> ...and switching the order doesn't exactly work, because one cannot
> then have a (:markup:) [=...=] block followed by a 
> (:markup:) ... (:markupend:) block (the system treats it all as being
> a single markup block).  
> 
> I'm open for suggestions.

I think we should just swallow the pill and force a change of all
	(:markup:) [=...=]
into
	(:markup:) ... (:markupend:)

Something similar would be needed for (:dmarkup:), or we could possibly 
use:

	(:markup:) .... (:markupshow:) ... (:markupend:)

for when we want to use different rendering code.

If that's not acceptable, we should instead address the problem with the
[=...=]. If I understand that correctly, it is related to [= ... =] not
actually being parsed, but just matched against a regexp? (Which makes it
difficult to handle nested pairs, which is what we'd really like here)

Personally, I'd very much appreciate [=...=] that can be nested...

/Christian

-- 
Christian Ridderström, +46-8-768 39 44               http://www.md.kth.se/~chr




More information about the pmwiki-users mailing list