From: Dan Stromberg <drsalists@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Proliferation of options is great simplification of pipes, really?
Date: Sun, 21 Feb 2021 20:32:27 -0800 [thread overview]
Message-ID: <CAGGBd_r4G+SOitsYYE=+ut_73SOMC5NCWHKkbUYrgh3Y=_q54w@mail.gmail.com> (raw)
In-Reply-To: <20210222033217.dkqavclp22sa77ln@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On Sun, Feb 21, 2021 at 7:33 PM G. Branden Robinson <g.branden.robinson@gmai
>
> > The groff program allows to control the whole groff system by command
> > line options. This is a great simplification in comparison to the
> > classical case (which uses pipes only).
>
> What strikes _me_ about the above is the awful Denglish in it. I fixed
> this back in 2017 and the correction shipped as part of groff 1.22.4 in
> December 2018.
>
I like the easy composability of pipes, but I don't mind some options.
I don't like the huge, all-purpose applications called web browsers nearly
as much. They strike me as Very un-unixy. But much can be justified by
not having to get users to download a client application, and not having to
get sysadmins to punch a hole through their firewalls.
I'd say it's neither, and reflects (1) the limitations of the Unix
> filter model, or at least the linear topology of Unix pipelines[1]
>
I don't think they have to be linear:
http://joeyh.name/code/moreutils/ (see the unfortunately-named "pee"
utility)
and:
https://stromberg.dnsalias.org/~strombrg/mtee.html
Full disclosure: I wrote mtee.
[-- Attachment #2: Type: text/html, Size: 1831 bytes --]
next prev parent reply other threads:[~2021-02-22 4:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 2:34 Will Senn
2021-02-22 3:32 ` G. Branden Robinson
2021-02-22 4:32 ` Dan Stromberg [this message]
2021-02-22 4:34 ` Will Senn
2021-02-22 5:45 ` G. Branden Robinson
2021-02-22 15:49 ` John P. Linderman
2021-02-22 15:57 ` William Cheswick
2021-02-22 16:03 ` John P. Linderman
2021-02-22 21:16 ` G. Branden Robinson
2021-02-22 16:02 ` Warner Losh
2021-02-22 16:12 ` Robert Clausecker
2021-02-22 17:15 ` John Cowan
2021-02-23 0:24 ` Steffen Nurpmeso
2021-02-22 21:14 ` G. Branden Robinson
2021-02-22 7:20 ` Rich Morin
2021-02-22 18:27 ` Jon Steinhart
2021-02-22 19:30 ` Richard Salz
2021-02-23 2:47 M Douglas McIlroy
2021-02-23 10:42 ` Jaap Akkerhuis
2021-02-23 13:23 ` Brantley Coile
2021-02-23 13:49 ` Ralph Corderoy
2021-02-23 15:04 Steve Simon
2021-02-24 2:42 ` M Douglas McIlroy
2021-02-24 19:38 Norman Wilson
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='CAGGBd_r4G+SOitsYYE=+ut_73SOMC5NCWHKkbUYrgh3Y=_q54w@mail.gmail.com' \
--to=drsalists@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=tuhs@minnie.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).