From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 9281 invoked from network); 17 Sep 2022 13:51:24 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 17 Sep 2022 13:51:24 -0000 Received: from chrisfroeschl.de ([185.183.157.17]) by 9front; Sat Sep 17 09:50:16 -0400 2022 Received: from cirno.fritz.box ([46.128.193.201]) by chrisfroeschl.de; Sat Sep 17 15:50:14 +0200 2022 Message-ID: Date: Sat, 17 Sep 2022 15:50:00 +0200 From: chris@chrisfroeschl.de To: 9front@9front.org In-Reply-To: <4D4996DE-362B-41A7-93D0-38A87376C560@stanleylieber.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: asynchronous singleton-scale YAML over AJAX package cloud Subject: Re: [9front] [PATCH] nedmail(1): add plenty of missing commands + (theoretical) flag descriptions Reply-To: 9front@9front.org Precedence: bulk > should we document flags that don’t work? they exist partly in the 'help' cmd from nedmail and are part of the common upas src. I just intended to give them any meaning since I was always wondering what they mean. Otherwise I could perhaps adjust some nedmail code to not mention stuff that doesn't work or exists atm. chris