Hi, James!
At 2021-10-18T10:05:55-0400, James K. Lowden wrote:
> Is there a way to say, "set this URL all on one line if at all
> possible, else break at these specific points"? Sort of a ".ne" for
> horizontal space?
Yes, there is!
[man]: Try to minimize the number of times a URI is broken whe
Hi, Ralph,
At 2021-10-23T10:46:32+0100, Ralph Corderoy wrote:
> Hi Branden,
>
> > But in fact, trailing slashes on URIs are semantically
> > significant[1]
> ...
> > [1]
> > https://stackoverflow.com/questions/5948659/when-should-i-use-a-trailing-slash-in-my-url/
>
> StackOverflow isn't
Hi Branden,
> 2. URIs can validly, and in fact commonly do, end with single slashes.
...
> But in fact, trailing slashes on URIs are semantically
> significant[1]
...
> [1]
> https://stackoverflow.com/questions/5948659/when-should-i-use-a-trailing-slash-in-my-url/
StackOverflow isn't an
On Mon, 18 Oct 2021 16:34:17 +1100
"G. Branden Robinson" wrote:
> URIs can be lengthy; rendering them can result in jarring adjust?
>ment or variations in line length, or troff warnings when a
> hy? perlink is longer than an output line. The application of non-
>printing brea
Hi, Branden!
On 10/18/21 7:34 AM, G. Branden Robinson wrote:
Hi, Alex!
At 2021-10-17T21:33:24+0200, Alejandro Colomar wrote:
Break URIs before a single slash, not after.
I found no GNU-specific (or any other at all) source that recommends
breaking long URIs after a slash. So follow Chicago S
Hi, Alex!
At 2021-10-17T21:33:24+0200, Alejandro Colomar wrote:
> Break URIs before a single slash, not after.
>
> I found no GNU-specific (or any other at all) source that recommends
> breaking long URIs after a slash. So follow Chicago Style and
> break them before single slashes.
As far as I
Break URIs before a single slash, not after.
I found no GNU-specific (or any other at all) source that recommends
breaking long URIs after a slash. So follow Chicago Style and
break them before single slashes.
Scripted fix:
$ find * -type f \
| xargs grep -l '^\.UR.*[^/]/\\:' \
| xargs sed
