The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] dmr note on BSD's sins
Date: Wed, 3 May 2017 10:57:07 -0400	[thread overview]
Message-ID: <CAC20D2Nk3+P67Z_OxDym4MEPJbne7GZW3tyK35B3ZfO_MfZ8PQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1705031055190.11767@aneurin.horsfall.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]

below...


On Tue, May 2, 2017 at 8:59 PM, Dave Horsfall <dave at horsfall.org> wrote:

> On Tue, 2 May 2017, Doug McIlroy wrote:
>
> > With Steve's eloquent grump and cat -v on the table, I can't help
> > re-citing the peerless cardinal sin of
> >         less --help | wc
>

To Doug -- touché




> Speaking of "cat", what really drives me nuts is "cat file | cmd"...
>
> What's wrong with "cmd < file" (or to really confuse newbies, "< file
> cmd")?


Not to be argumentative, but Dave, please be careful.  I agree that
idiom is misused, but there are times when I think it is appropriate, which
is one of the reason why I love the Unix guiding principle of not "forcing"
the user to do one thing or another because we know better, but letting
education and good 'taste' be the guide.

​I think Justice Potter Stewart describe​d pornography of knowing it when
he sees it.  IMO: there are time when using cat is in better taste that a
file redirection.  For instance, I can think of a few examples when I need
to direct input from multiple files, using a more complex 'wye' style pipe
line or a redirection from backward quotes, that the cat foo sequence seems
like its easier to understand/debug.  [Maybe it shows my inner
schizophrenia and heard voices from multiple places that I kinda like the
'wye' command].

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170503/9465a193/attachment.html>


  parent reply	other threads:[~2017-05-03 14:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03  0:52 Doug McIlroy
2017-05-03  0:59 ` Dave Horsfall
2017-05-03 12:54   ` Dan Cross
2017-05-03 13:09     ` Arthur Krewat
2017-05-03 13:46   ` Michael Kjörling
2017-05-03 14:57   ` Clem Cole [this message]
2017-05-03 15:34     ` arnold
2017-05-03 15:44       ` Clem Cole
  -- strict thread matches above, loose matches on Subject: below --
2017-05-03 13:41 Nemo
2017-05-03 22:18 ` Dave Horsfall
2017-05-04 14:59 ` Tim Bradshaw
2017-05-04 23:14   ` Larry McVoy
2017-05-05 14:01     ` Random832
2017-05-05 18:56       ` A. P. Garcia
2017-05-05 17:33     ` Tim Bradshaw
2017-05-01 17:25 ron minnich
2017-05-01 18:09 ` Toby Thain
2017-05-02 16:11   ` Steve Johnson
2017-05-02 16:39     ` Erik E. Fair
2017-05-02 16:43       ` ron minnich
2017-05-02 20:28     ` Diomidis Spinellis
     [not found]       ` <CAM4FNStH7KH6+ab0o_fYKfzutvPQ__0w0Zq5_6hk4AFP=+aSAw@mail.gmail.com>
2017-05-02 20:34         ` Daniel Camolês
2017-05-02 20:34       ` Steve Johnson
2017-05-02 21:22       ` Andy Kosela

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=CAC20D2Nk3+P67Z_OxDym4MEPJbne7GZW3tyK35B3ZfO_MfZ8PQ@mail.gmail.com \
    --to=clemc@ccc.com \
    /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).