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 1nx8Sc-0000Aw-0W for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Jun 2022 14:39:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nx8Sa-0006s1-BU for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Jun 2022 14:39:32 +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 1nx8SZ-0006rs-O6 for pgsql-hackers@lists.postgresql.org; Fri, 03 Jun 2022 14:39:31 +0000 Received: from mail-il1-x135.google.com ([2607:f8b0:4864:20::135]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nx8SU-0008O5-P2 for pgsql-hackers@lists.postgresql.org; Fri, 03 Jun 2022 14:39:30 +0000 Received: by mail-il1-x135.google.com with SMTP id p1so6859773ilj.9 for ; Fri, 03 Jun 2022 07:39:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=4Wb4c3fzuhEnTmtvNZN7r60G9Om1WPt/rui5ndEBgoU=; b=hNtagRMzOc9I4LUgeeZI31KL/ywm+336KF1RTtuJWS7lGZZOuKR2TfSAloFUgq/7zh 9+viR0LGcfrpVfrMix04k8tNWTES1/b2LsVy+GDzjIrBUaIcy/5yPweBkHmwjCnvuI9b JptSttg2eQWddibdTUqSXm2pd4+86eEoQRgyTuw/NUUQ6d4PJ1wVylYe842hPkBK9ugQ Jsor/Maf8zwqrbaJbEh/urOaYkgMF6qiMvkH1tQ78GT/3jSPPcFNuWe075lWhPP86fId E48KGC/0+sjUC0JGRlfme8isDfZluv5v6k30DD5exPnfIN/DNtUQdjBcUPJVRg5mKGvw HwSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=4Wb4c3fzuhEnTmtvNZN7r60G9Om1WPt/rui5ndEBgoU=; b=pvNrYtm8aTrOV+oXcTDk0/hYbjMmQONS3iuobhZ5JZbQV9nq5ovyyD3hYAHnr2sH86 wifE6VdiFBg2FbO1hp4VjWTo+w+xy1SaM3H9lTEvTGmQO4Ge+KWp4kxHWf3ZW2inkvQ6 dQWZkZmLCvTXPMFwm11YxgBl52oosJfNQlkk4jlGf5EdV2dGDb8ySq7SyXXDOpva9ZlT U5zDwG3K7Q1nTLQSqQ4R5b83Hx4+bHtly3XTd46u7sbosBYYsHN55NoCqP4A9TvPJ0YC yYFtliRCdSDLW3M6arUWP5MhRMbZQJpiKo73rXhiqpxs/D4TlAf7jLhEMK9QD96TpcEz t+5w== X-Gm-Message-State: AOAM530ONvInjM13ex4tjNmMn7N2gyKf9k/Z6jojpCbr1VSboxQ9gf01 NKDMsY0JIskEzv6X6PAmnXbz4meuq2E= X-Google-Smtp-Source: ABdhPJzHsDGh895DpZVAYcCmVptcO28P1olg+kAXydqty/3IlLHJHQxGgMdjqZ3Kon+hyfk6UqLrSA== X-Received: by 2002:a05:6638:25d3:b0:32e:e5ee:496c with SMTP id u19-20020a05663825d300b0032ee5ee496cmr5966030jat.52.1654267165948; Fri, 03 Jun 2022 07:39:25 -0700 (PDT) Received: from nathanxps13 ([2600:1700:48f8:340f:9b46:7c88:c58:3775]) by smtp.gmail.com with ESMTPSA id ce14-20020a0566381a8e00b00330ad5429fdsm2572887jab.106.2022.06.03.07.39.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 03 Jun 2022 07:39:25 -0700 (PDT) Date: Fri, 3 Jun 2022 07:39:21 -0700 From: Nathan Bossart To: "Thibaud W." Cc: pgsql-hackers@lists.postgresql.org Subject: Re: Proposal: adding a better description in psql command about large objects Message-ID: <20220603143921.GA2624579@nathanxps13> References: <43f0439c-df3e-a045-ac99-af33523cc2d4@dalibo.com> <20220602214625.GA2494933@nathanxps13> <2e872233-1642-439c-dd94-56fc25d398cb@dalibo.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <2e872233-1642-439c-dd94-56fc25d398cb@dalibo.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jun 03, 2022 at 10:12:30AM +0200, Thibaud W. wrote: > In fact the original tabs were missing in the first file. > In version v2, it seems interesting to keep calls to the fprintf function > for translation. I attached a new file. Yes, it looks like the precedent is to have an fprintf() per command. I still think the indentation needs some adjustment for readability. In the attached, I've lined up all the large object commands. This is offset from most other commands, but IMO this is far easier to read, and something similar was done for the operator class/family commands. Thoughts? -- Nathan Bossart Amazon Web Services: https://aws.amazon.com --wRRV7LY7NUeQGEoC Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="v4-0001-Add-descriptions-for-psql-s-large-object-backslas.patch" From 046e450e6d578fe365ef6c561a477d70d09f3076 Mon Sep 17 00:00:00 2001 From: Nathan Bossart Date: Thu, 2 Jun 2022 14:35:31 -0700 Subject: [PATCH v4 1/1] Add descriptions for psql's large object backslash commands. These should be mostly self-explanatory, but they are the only backslash commands lacking individual short descriptions. Author: Thibaud W. Reviewed by: Nathan Bossart Description: https://postgr.es/m/43f0439c-df3e-a045-ac99-af33523cc2d4%40dalibo.com --- src/bin/psql/help.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/bin/psql/help.c b/src/bin/psql/help.c index 49eb116f33..33902d496a 100644 --- a/src/bin/psql/help.c +++ b/src/bin/psql/help.c @@ -321,10 +321,10 @@ slashUsage(unsigned short int pager) fprintf(output, "\n"); fprintf(output, _("Large Objects\n")); - fprintf(output, _(" \\lo_export LOBOID FILE\n" - " \\lo_import FILE [COMMENT]\n" - " \\lo_list[+]\n" - " \\lo_unlink LOBOID large object operations\n")); + fprintf(output, _(" \\lo_export LOBOID FILE export large object to file\n")); + fprintf(output, _(" \\lo_import FILE [COMMENT] import large object from file\n")); + fprintf(output, _(" \\lo_list[+] list large objects\n")); + fprintf(output, _(" \\lo_unlink LOBOID delete a large object\n")); ClosePager(output); } -- 2.25.1 --wRRV7LY7NUeQGEoC--