Let shortcut types have useful behavior in the parameterless case

[jdporter]

One of our esteemed monks yesterday proposed to let the cpan:// shortcut type (or "pseudoscheme") have meaningful behavior when written with no parameters ([cpan://]). Seemed reasonable enough, but I don't feel that cpan:// should be special in this regard; so I'm proposing that all shortcut types be similarly extended — or at least those for which some such reasonable behavior can be identified. Specifically, I propose that the following PerlMonks pseudoschemes render as the corresponding link in the parameterless case:

acronym	Acronym Finder
apc	Perl Repository Browser
c2	Wiki Wiki Web
cpan	CPAN
dict	DICT.org
dist	CPAN
doc	Perl documentation
e2	Everything
google	Google
imdb	IMDB
isbn	ISBN
jargon	The Jargon File
kobes	kobesearch
lj	LiveJournal
mod	CPAN
perldoc	Perl documentation
wb	Wikibooks
wp	Wikipedia
wq	Wikiquote
ws	Wikisource

Note that the specific link texts shown above are merely the default; per the usual operation of shortcuts, explicit link text, if given, overrides the default.

Pseudoschemes not listed above either:

1. are special in the parameterless case (e.g. localtime, pad)
2. don't have obvious useful semantics in the parameterless case (e.g. http, id)
3. are aliases of pseudoschemes listed (e.g. docs, kobe)

[jdporter]

handlelinks settings - (patch)

Test Cases:

Scheme:	Using default text:	With explicit text:
acronym://	Acronym Finder	acronym
apc://	Perl Source Code (git)	apc
c2://	Wiki Wiki Web	c2
cpan://	CPAN	cpan
dict://	Dict.org	dict
dist://	CPAN	dist
doc://	Perl documentation	doc
docs://	Perl documentation	docs
e2://	Everything2	e2
ftp://	[ftp://]	ftp
google://	Google	google
href://	[href://]	href
http://	[http://]	http
https://	[https://]	https
id://	[id://]	id
imdb://	IMDB	imdb
isbn://	ISBN	isbn
jargon://	The Jargon File	jargon
kobe://	Kobesearch	kobe
kobes://	Kobesearch	kobes
link://	[href://]	link
lj://	LiveJournal	lj
lucky://	Google	lucky
mod://	CPAN	mod
module://	CPAN	module
pad://	my scratchpad	pad
perldoc://	Perl documentation	perldoc
rt://	RT.CPAN	rt
wb://	Wikibooks	wb
wikipedia://	Wikipedia	wikipedia
wp://	Wikipedia	wp
wq://	Wikiquote	wq
ws://	Wikisource	ws

[demerphq]

apc:// has had a no-target default since it was created.

And I agree with tye that any handler that doesnt have a sane no-target possibility should foward to the appropriate documentation page.

[jdporter]

any handler that doesnt have a sane no-target possibility should foward to the appropriate documentation page

That's a reasonable thing to do, but to my mind a better approach would be to let [foo://] DWIM from the writer's POV. IOW, if I want to link to the Perl Changes Browser, I write [apc://] If I want to link to the Wiki Wiki Web, I write [c2://]. If I want to link to the Perl docs, I write [doc://]. If I want to link to Wikipedia, I write [wp://]. And so on. Rather than assuming the author made an error.

There's precedent for both approaches ([id://] vs. [apc://]). However, given that [id://] doesn't have any other useful default semantics, I'm not convinced that this is the precedent to follow. I'd rather follow the [apc://] precedent.

[ikegami]

I think you misread. demerphq specified the handlers without "a sane no-target possibility" (e.g. the handlers for "http", "id" and similar) should link to docs on how to use them, not all of handlers.

[ikegami]

[http://] should go to a locally hosted copy of this. :)

[tye]

[id://] already goes to [id://], so [http://] could have a similar behavior.

[holli]

Why not let [http://] point to http://? As everybody knows that's the best search engine in the whole wide world. ;-)

/me ducks