Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ppTrc-0003FA-Jw for pgsql-hackers@arkaria.postgresql.org; Thu, 20 Apr 2023 12:58:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ppTra-00060j-Sj for pgsql-hackers@arkaria.postgresql.org; Thu, 20 Apr 2023 12:58:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ppTra-00060Z-In for pgsql-hackers@lists.postgresql.org; Thu, 20 Apr 2023 12:58:14 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ppTrS-000saY-QY for pgsql-hackers@lists.postgresql.org; Thu, 20 Apr 2023 12:58:13 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id CEDFA2F45DA2 for ; Thu, 20 Apr 2023 14:57:47 +0200 (CEST) Received: from s934.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id BED972E28BF9; Thu, 20 Apr 2023 14:57:47 +0200 (CEST) Received: from s473.loopia.se (unknown [172.22.191.5]) by s934.loopia.se (Postfix) with ESMTP id B92B77CEAD9; Thu, 20 Apr 2023 14:57:47 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s899.loopia.se ([172.22.191.6]) by s473.loopia.se (s473.loopia.se [172.22.190.13]) (amavisd-new, port 10024) with LMTP id rdvkBp--ooin; Thu, 20 Apr 2023 14:57:47 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s899.loopia.se (Postfix) with ESMTPSA id 11D1A2C8BA85; Thu, 20 Apr 2023 14:57:47 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.2\)) Subject: Re: Should we put command options in alphabetical order in the doc? From: Daniel Gustafsson In-Reply-To: Date: Thu, 20 Apr 2023 14:57:46 +0200 Cc: Alvaro Herrera , Peter Geoghegan , PostgreSQL Developers Content-Transfer-Encoding: 7bit Message-Id: References: <20230419084747.suskrykkzm2ity5e@alvherre.pgsql> To: David Rowley X-Mailer: Apple Mail (2.3696.120.41.1.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 20 Apr 2023, at 14:40, David Rowley wrote: > I see "man grep" categorises the command line options and then sorts > alphabetically within the category. On FreeBSD and macOS "man grep" lists all options alphabetically. > FWIW, vacuumdb --help has its options in alphabetical order using the > abbreviated form of the option. It does (as most of our binaries do) group "Connection options" separately though, and in initdb --help and pg_dump --help we have other groupings as well. -- Daniel Gustafsson