Last modified: 2006-12-03 04:27:07 UTC
1. $1 returns the searched text with leading colon. I wonder about needs, didn't find any. It's not possible to simply write something like "There's no page in Wikipedia with name $1" because it confuses people when they search for "foo" and get "There's no page in Wikipedia with name :Foo" or searching for "Template:bar" returns "There's no page in Wikipedia with name :Template:bar" etc. 2. $1 used in one built-in template works, in other does not When need to point to any log page the first idea is: [{{fullurl:Special:Log|type=move&page=$1}} Move log] but in case of $1 of more words (Lorem ipsum) it returns link going to log of page "Lorem" with anchor text "ipsum Move log" Ok, so apparently encoding needed: [{{fullurl:Special:Log|type=move&page={{urlencode:$1}}}} Move log] but it returns link going to log of page "$1" with anchor text "Move log" Danny B.
Please file separate requests separately in the future. 1) It is a bit weird, yes. Fair enough to leave it as a bug. 2) This is bug 6261.
Ironed out when "nogomatch" was renamed to "noexactmatch"; the leading colon was dropped and the message format changed.