is currently broken in trunk. Screenshot:
The issue is only in trunk, same report works properly in the 5.1 branch, e.g. it is a code issue, not a WEBLIST usage issue.
This is fixed now.
Currently special strings in the format parameters are handled as follows.
- $web and $name need to be at a word boundary (\b) to be expanded. $web1 and $name1 are not expanded.
- $marker, $qname, $indentedname don't have be at a word boundary to be expanded.
Is there a way to avoid this inconsistency?
Now that FormatTokens
can be used (r23518 onward), we can make the behaviors of $marker, $qname, and $indentedname consistent with $web and $name without sacrificing expressiveness - $marker$nopSOMETHING.
I understand compatibility matters. But I wonder what you think, Peter.
Looking at SEARCH, it has lots of variables that do not require word boundaries:
$out = $format;
$out =~ s/\$web/$web/gs;
$out =~ s/\$topic\(([^\)]*)\)/TWiki::Render::breakName( $topic, $1 )/ges;
$out =~ s/\$topic/$topic/gs;
$out =~ s/\$date/$revDate/gs;
$out =~ s/\$isodate/$isoDate/gs;
$out =~ s/\$rev/$revNum/gs;
$out =~ s/\$wikiusername/$wikiusername/ges;
$out =~ s/\$ntopics/$ntopics/gs;
$out =~ s/\$nhits/$nhits/gs;
$out =~ s/\$wikiname/$wikiname/ges;
I recommend to stay compatible.
BTW, I don't like the syntax for
because one could write as well
, e.g. overkill. Same with
, it clobbers indent and topic name, so it is not easy to create custom link formats with indents. For inconsistent variables like these I recommend to retire them by keeping feature as undocumented feature, and to introduce new variables that are more consistent.
Thanks, that fixed another issue: The Home pulldown menu show gray web color for all webs instead of actual web colors.
I am setting this to "Closed" since it was a bug introduced and fixed in trunk only, e.g. not to be announced in a release.