On 10 January 2015 at 11:38, David E. Wheeler da...@justatheory.com wrote:
and no newlines at all inside L. Any objections?
I conditionally object to that last one _IF_ It incorporates banning of
this structure:
L
ASDF
|URL
Presently that format is quite useful when either URL or link text
On 10 January 2015 at 12:25, Kent Fredric kentfred...@gmail.com wrote:
Parses correctly.
Likewise:
Ltext here
|URL Here
Is also presently valid and has the desired product.
Bah, I seem to have fucked up my response grammar very badly in the edit
process. Pretend my remarks are sensible
On Jan 9, 2015, at 3:25 PM, Kent Fredric kentfred...@gmail.com wrote:
Presently that format is quite useful when either URL or link text is very
large, and avoids tripping some
line-length metrics that can't otherwise easily be satisfied in a non-global
manner.
I’m not proposing to remove
On Jan 8, 2015, at 1:07 PM, David E. Wheeler da...@justatheory.com wrote:
IIUC, the case that came up was
Lfoo bar|http://baz.com/foo
bar
I am kind of inclined to just say that such things are verboten.
Done by closing this issue. https://rt.cpan.org/Ticket/Display.html?id=93491
* David E. Wheeler da...@justatheory.com [2015-01-08T13:42:10]
I think that is probably sane, but maybe there are other opinions? Should we
allow whitespace in L URLs? If so, I think we would just change \S to .
I didn't scrutinize the regexp (which is present in perlpodspec) closely, but
URLs
On Jan 8, 2015, at 1:00 PM, Ricardo Signes perl@rjbs.manxome.org wrote:
I didn't scrutinize the regexp (which is present in perlpodspec) closely, but
URLs may not contain unescape spaces, so I think there's no reason to allow
it.
Lfoo bar|http://baz-barshould be okay
Lfoo
On Thu, 8 Jan 2015 10:42:10 -0800
David E. Wheeler da...@justatheory.com wrote:
I think that is probably sane, but maybe there are other opinions?
Should we allow whitespace in L URLs?
URLs use + or %20 for spaces. There is no need for whitespace in a URL.
--
Don't stop where the ink does.
