Template talk:plainlinks - Revision history

Defender1031: /* Implicit parameter version */ dunno how that got there

Defender1031 — Mon, 08 May 2017 14:44:40 GMT

Implicit parameter version: dunno how that got there

← Older revision		Revision as of 14:44, 8 May 2017
Line 1:		Line 1:
	==Implicit parameter version==		==Implicit parameter version==
	I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)		I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)
-	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}}</nowiki> would end up being parsed as having been passed a parameter named "<nowiki>https://google.com/search?q</nowiki>" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Of course, since "<nowiki>https://google.com/search?q</nowiki>" is not a parameter that this template expects, it would end up doing nothing, and the template itself would show gibberish rather than the expected link. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. {{User:DeFender1031/sig}} 11:47, 8 May 2017 (UTC)	+	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}}</nowiki> would end up being parsed as having been passed a parameter named "<nowiki>https://google.com/search?q</nowiki>" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Of course, since "<nowiki>https://google.com/search?q</nowiki>" is not a parameter that this template expects, it would end up doing nothing, and the template itself would show gibberish rather than the expected link. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. {{User:DeFender1031/sig}} 11:47, 8 May 2017 (UTC)
	::Okay. Thanks! {{User:Gfdgsgxgzgdrc/sig‎}} 14:38, 8 May 2017 (UTC)		::Okay. Thanks! {{User:Gfdgsgxgzgdrc/sig‎}} 14:38, 8 May 2017 (UTC)

Gfdgsgxgzgdrc: Ohh. Now I understand.

Gfdgsgxgzgdrc — Mon, 08 May 2017 14:38:40 GMT

Ohh. Now I understand.

← Older revision		Revision as of 14:38, 8 May 2017
Line 2:		Line 2:
	I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)		I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)
	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}}</nowiki> would end up being parsed as having been passed a parameter named "<nowiki>https://google.com/search?q</nowiki>" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Of course, since "<nowiki>https://google.com/search?q</nowiki>" is not a parameter that this template expects, it would end up doing nothing, and the template itself would show gibberish rather than the expected link. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. {{User:DeFender1031/sig}} 11:47, 8 May 2017 (UTC)		:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}}</nowiki> would end up being parsed as having been passed a parameter named "<nowiki>https://google.com/search?q</nowiki>" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Of course, since "<nowiki>https://google.com/search?q</nowiki>" is not a parameter that this template expects, it would end up doing nothing, and the template itself would show gibberish rather than the expected link. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. {{User:DeFender1031/sig}} 11:47, 8 May 2017 (UTC)
		+	::Okay. Thanks! {{User:Gfdgsgxgzgdrc/sig‎}} 14:38, 8 May 2017 (UTC)

Defender1031: yeah, I don't want those being links either.

Defender1031 — Mon, 08 May 2017 11:48:42 GMT

yeah, I don't want those being links either.

← Older revision		Revision as of 11:48, 8 May 2017
Line 1:		Line 1:
	==Implicit parameter version==		==Implicit parameter version==
	I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)		I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)
-	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}}</nowiki> would end up being parsed as having been passed a parameter named "https://google.com/search?q" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Of course, since "https://google.com/search?q" is not a parameter that this template expects, it would end up doing nothing, and the template itself would show gibberish rather than the expected link. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. {{User:DeFender1031/sig}} 11:47, 8 May 2017 (UTC)	+	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}}</nowiki> would end up being parsed as having been passed a parameter named "<nowiki>https://google.com/search?q</nowiki>" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Of course, since "<nowiki>https://google.com/search?q</nowiki>" is not a parameter that this template expects, it would end up doing nothing, and the template itself would show gibberish rather than the expected link. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. {{User:DeFender1031/sig}} 11:47, 8 May 2017 (UTC)

Defender1031: well... that'll certainly cause weird issues, such as the unparsed tildes.

Defender1031 — Mon, 08 May 2017 11:47:41 GMT

well... that'll certainly cause weird issues, such as the unparsed tildes.

← Older revision		Revision as of 11:47, 8 May 2017
Line 1:		Line 1:
	==Implicit parameter version==		==Implicit parameter version==
	I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)		I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)
-	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}} would end up being parsed as having been passed a parameter named "https://google.com/search?q" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Of course, since "https://google.com/search?q" is not a parameter that this template expects, it would end up doing nothing, and the template itself would show gibberish rather than the expected link. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. ~~~~~~~~	+	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}}</nowiki> would end up being parsed as having been passed a parameter named "https://google.com/search?q" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Of course, since "https://google.com/search?q" is not a parameter that this template expects, it would end up doing nothing, and the template itself would show gibberish rather than the expected link. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. {{User:DeFender1031/sig}} 11:47, 8 May 2017 (UTC)

Defender1031: /* Implicit parameter version */ a bit of a clarification of what would end up happening technically

Defender1031 — Mon, 08 May 2017 09:15:19 GMT

Implicit parameter version: a bit of a clarification of what would end up happening technically

← Older revision		Revision as of 09:15, 8 May 2017
Line 1:		Line 1:
	==Implicit parameter version==		==Implicit parameter version==
	I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)		I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)
-	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}} would end up being parsed as having been passed a parameter named "https://google.com/search?q" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. ~~~~	+	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}} would end up being parsed as having been passed a parameter named "https://google.com/search?q" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Of course, since "https://google.com/search?q" is not a parameter that this template expects, it would end up doing nothing, and the template itself would show gibberish rather than the expected link. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. ~~~~

Defender1031: /* Implicit parameter version */ correct how the example works

Defender1031 — Mon, 08 May 2017 09:09:48 GMT

Implicit parameter version: correct how the example works

← Older revision		Revision as of 09:09, 8 May 2017
Line 1:		Line 1:
	==Implicit parameter version==		==Implicit parameter version==
	I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)		I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)
-	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}} would end up being parsed as having been passed a parameter named "https://google.com?q" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. ~~~~	+	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}} would end up being parsed as having been passed a parameter named "https://google.com/search?q" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. ~~~~

Defender1031: I hope this clears it up.

Defender1031 — Mon, 08 May 2017 08:53:26 GMT

I hope this clears it up.

← Older revision		Revision as of 08:53, 8 May 2017
Line 1:		Line 1:
		+	==Implicit parameter version==
	I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)		I'm not sure why my version was reverted. This way, if you type <nowiki>{{p\|l=http://www.homestarrunner.com}} or {{p\|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)
		+	:That may work for that particular URL, but any URL that has an equals sign in it would completely break the template if passed that way. (For example, <nowiki>{{p\|https://google.com/search?q=Homestar+Runner}} would end up being parsed as having been passed a parameter named "https://google.com?q" with the value of "Homestar+Runner", rather than taking the entire link as the "1" parameter as you seem to expect that it would. Given how many links on the modern web involve query parameters, there are probably more links that would break the template if used in this manner than there are links that would not. (I know that for myself, the vast majority of times I have used this template were to link to a particular page revision on this wiki, which most definitely contain equals signs.) Given that the difference between URLs that will work and URLs that will break is subtle, technical, and not immediately obvious, it would be a bad idea to allow an alternate form that only works sometimes. Imagine someone who is familiar with the implicit form suddenly getting no link out of the template at all and having no idea why it's not working nor how to fix it, because they don't know this thing about the equals signs. All in all, it's better for everyone if we require those two extra characters ("l=") whenever this template is in use. Hope that clears it up for you. ~~~~

Gfdgsgxgzgdrc: It works fine both ways.

Gfdgsgxgzgdrc — Sun, 07 May 2017 22:54:37 GMT

It works fine both ways.

New page

I'm not sure why my version was reverted. This way, if you type <nowiki>{{p|l=http://www.homestarrunner.com}} or {{p|http://www.homestarrunner.com}}</nowiki>, it would still work either way. I'm not sure what's confusing about that. {{User:Gfdgsgxgzgdrc/sig‎}} 22:54, 7 May 2017 (UTC)