Page MenuHomePhabricator

Have searchbox recognize {{ to search Template: namespace
Open, LowPublic

Description

When editing wikitext, I can copy any wikilink--the text in square brackets, without pipe text--into the searchbox to go to that article. It even works if the link has namespace or sisterproject components. However, template-transclusion has an implicit Template: namespace. If I copy the text from the curly-braces (without parameters) into the searchbox, I have to manually insert the "Template:" prefix, and do so if and only if there isn't some other namespace already given.

As a feature request, I would like the searchbox to treat "{{Foo" as "Template:Foo". That is, if the search-string begins with "{{", convert it to "Template:" if there is no namespace and then remove it regardless. For symmetry, a trailing "}}" should be ignored. For consistency of "copy-base of wikitext", leading "[[" and trailing "]]" should also be ignored.

Event Timeline

EBjune added a subscriber: EBjune.

Since there seems to already be a way to get what you need from the search, albeit with a bit of manual insertion, I'm setting the priority on this to low, and in the meantime we will look deeper into whether others would like this feature as well.

Since there seems to already be a way to get what you need from the search, albeit with a bit of manual insertion, I'm setting the priority on this to low, and in the meantime we will look deeper into whether others would like this feature as well.

https://commons.wikimedia.org/wiki/Commons:Village_pump/Proposals/Archive/2019/10#Proposal_typing_aid suggests support, though it wasn't fully clear Sarang meant only shortcuts for the search instead of full namespace redirects.

  • Treat {{ as Template:
  • Ignore trailing }}
  • Ignore leading [[
  • Ignore trailing ]]

What about:
- Treat F/ as File:
- Treat T/ as Template:
- Treat C/ as Category:
- Treat COM/ as Commons: (yes, COM: already exists, but people who regularly navigate using the search would get used to the slash)
- Treat H/ as Help:
- Treat U/ as User:
- Treat UT/ as User talk:
- Treat M/ as Module: bad idea

Would seem useful to me.

  • Treat {{ as Template:
  • Ignore trailing }}
  • Ignore leading [[
  • Ignore trailing ]]

Sounds like a good plan to me.

What about:

  • Treat F/ as File:

No that would be too short. Mainspace pages may conflict with this redirect. Just File seems fine to me.

  • Treat T/ as Template:

Per above. Too short. TEM seems reasonable.

  • Treat C/ as Category:

Per above. CAT is a lot better.

  • Treat COM/ as Commons: (yes, COM: already exists, but people who regularly navigate using the search would get used to the slash)

Why the extra slash?

  • Treat H/ as Help:
  • Treat U/ as User:

These are too short. No need to create redirects IMO.

  • Treat UT/ as User talk:

Hmm, I am nuetral about this one.

  • Treat M/ as Module:

MOD would be better IMO.

Would seem useful to me.

And there you have it, my opinion on the matter.

  • Treat {{ as Template:
  • Ignore trailing }}
  • Ignore leading [[
  • Ignore trailing ]]

Sounds like a good plan to me.

What about:

  • Treat F/ as File:

No that would be too short. Mainspace pages may conflict with this redirect. Just File seems fine to me.

I'll be darned: https://commons.wikimedia.org/wiki/F/A-18_Hornet

Okay, no slash.

@AlexisJazz should we discuss the rest on VPT or on any other page you have in mind?

@AlexisJazz should we discuss the rest on VPT or on any other page you have in mind?

I think the new proposals for TEM: and MOD: are mostly sufficient, but feel free to start a discussion on VPT.