Re: Add PostgreSQL home page to --help output
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Greg Stark <stark@mit.edu>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-02-20T11:09:25Z
Lists: pgsql-hackers
> On 20 Feb 2020, at 10:53, Daniel Gustafsson <daniel@yesql.se> wrote: > >> On 20 Feb 2020, at 10:15, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote: >> >> On 2020-02-13 14:24, Greg Stark wrote: >>> Sounds like a fine idea. But personally I would prefer it without the <> around the it, just a url on a line by itself. I think it would be clearer, look cleaner, and be easier to select to copy/paste elsewhere. >> >> I'm on the fence about this one, but I like the delimiters because it would also work consistently if we put a URL into running text where it might be immediately adjacent to other characters. So I was actually going for easier to copy/paste here, but perhaps in other environments it's not easier? > > For URLs completely on their own, not using <> makes sense. Copy pasting <url> > into the location bar of Safari makes it load the url, but Firefox and Chrome > turn it into a search engine query (no idea about Windows browsers). > > For URLs in running text it's not uncommon to have <> around the URL for the > very reason you mention. Looking at --help and manpages from random open > source tools there seems to be roughly a 50/50 split on using <> or not. RFC3986 discuss this in <https://tools.ietf.org/html/rfc3986#appendix-C>, with the content mostly carried over from RFC2396 appendix E. cheers ./daniel
Commits
-
Add PostgreSQL home page to --help output
- 1933ae629e7b 13.0 landed
-
Refer to bug report address by symbol rather than hardcoding
- 864934131ef7 13.0 landed