Subject: Re: [9front] [PATCH] nedmail(1): add plenty of missing commands + (theoretical) flag descriptions
Date: Sat, 17 Sep 2022 15:50:00 +0200 [thread overview]
Message-ID: <C6834D77DF48C60214A59DBD241F4BB0@chrisfroeschl.de> (raw)
> 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
next prev parent reply other threads:[~2022-09-17 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 13:37 Chris A. Fröschl
2022-09-17 13:46 ` Stanley Lieber
2022-09-17 13:50 ` chris [this message]
2022-09-17 14:01 ` chris
2022-09-19 6:37 ` chris
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).