The <nop> placed in front of a variable name does not stop the expansion of the variable. I know there are pipeline issues involved in dealing with these problems, but the current behavior seems nonintuitive.

Example:

Enter in topic: "<nop>%WIKIWEBLIST%"

When viewing output, it should show: "%WIKIWEBLIST%"

Instead, the above example shows as: "Main  |  TWiki06x01  |  Sandbox"

Workaround:

Enter in topic: "%<nop>WIKIWEBLIST%" instead.

NOTE: the raw source for this topic is a bit convoluted to deal with other discovered problems. Use this normal view for reference.

I suppose there may be a few more situations like this one lurking in <nop> processing similar to what was found for VerbatimExpandsVariables

Hey, I just found another case while writing this example!

"<nop><nop>" should show "<nop>" in the browser. If "view html source", it should show "&lt;nop&gt;". A workaround for this one is to explicitly type "&lt;nop&gt;" in the topic.

-- TomKagan - 27 Nov 2002

I do not consider this as a bug, the current spec is to espace variables like %<nop>VARIABLE%.

Interesting idea, I reclassified this as a FeatureBrainstorming. We could add a regex that escapes a variable if preceeded by a <nop> (e.g. change <nop>%VARIABLE% to <nop>%<nop>VARIABLE%), and another one to escape a <nop> if preceeded by another <nop> (e.g. change <nop><nop> to <nop&>)

-- PeterThoeny - 11 Dec 2002