From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: tuhs@tuhs.org
Subject: [TUHS] Re: troff doc discovery
Date: Thu, 29 Jun 2023 21:05:08 +0200 [thread overview]
Message-ID: <20230629190508.sJ_9A%steffen@sdaoden.eu> (raw)
In-Reply-To: <9FB0FDE6-6EF1-42F9-A200-FDAA916C0525@quintile.net>
Steve Simon wrote in
<9FB0FDE6-6EF1-42F9-A200-FDAA916C0525@quintile.net>:
|i always liked the approach of the plan9 script, bayesian in its approach \
|(perhaps).
|
|it is also admirably short.
Looking at
#?0|kent:9front.git$ git show origin/front:rc/bin/doctype
it seems to me a UNIX/POSIX sh(1) with getopt plus the same
grep|sort|awk pipe is not outperformed here.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
next prev parent reply other threads:[~2023-06-29 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 16:02 [TUHS] " Steve Simon
2023-06-29 19:05 ` Steffen Nurpmeso [this message]
2023-06-30 7:45 ` [TUHS] " arnold
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230629190508.sJ_9A%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).