Re: Add PostgreSQL home page to --help output

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Greg Stark <stark(at)mit(dot)edu>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add PostgreSQL home page to --help output
Date: 2020-02-20 09:53:10
Message-ID: 04D6B17B-5EE8-4889-AD2A-68C0F62F2B05@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 20 Feb 2020, at 10:15, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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.

cheers ./daniel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2020-02-20 10:39:45 Re: Experimenting with transactional memory for SERIALIZABLE
Previous Message Takashi Menjo 2020-02-20 09:30:09 RE: [PoC] Non-volatile WAL buffer