From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Unix taste
Date: Thu, 7 Aug 2014 23:27:50 -0400 (EDT) [thread overview]
Message-ID: <20140808032750.BB40D18C0FB@mercury.lcs.mit.edu> (raw)
> From: Doug McIlroy <doug at cs.dartmouth.edu>
> Yet a quoted "wc -l" as a bare command or (I suspect) as the first
> command in a pipeline would lead to "command not found".
I don't know about earlier versions of Unix, but FWLIW on V6 it does indeed
barf in both of these cases (just tried it).
Noel
next reply other threads:[~2014-08-08 3:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 3:27 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-14 4:34 Norman Wilson
2014-08-14 4:49 ` A. P. Garcia
2014-08-08 2:12 Doug McIlroy
2014-08-02 16:07 Ed
2014-08-02 15:38 Doug McIlroy
2014-08-02 16:07 ` John Cowan
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=20140808032750.BB40D18C0FB@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
/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).