From: michael@kjorling.se (Michael Kjörling)
Subject: [TUHS] dmr note on BSD's sins
Date: Wed, 3 May 2017 13:46:32 +0000 [thread overview]
Message-ID: <20170503134632.GF26584@yeono.kjorling.se> (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: 582 bytes --]
On 3 May 2017 10:59 +1000, from dave at horsfall.org (Dave Horsfall):
> What's wrong with "cmd < file" (or to really confuse newbies, "< file
> cmd")?
If you want to _really_ confuse a newbie, stick an "<file" or ">file"
_in the middle of_ a long command, and watch hilarity ensue.
Or the "<sth>" that someone here mentioned, if you are so inclined...
--
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
“People who think they know everything really annoy
those of us who know we don’t.” (Bjarne Stroustrup)
next prev parent reply other threads:[~2017-05-03 13:46 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 [this message]
2017-05-03 14:57 ` Clem Cole
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=20170503134632.GF26584@yeono.kjorling.se \
--to=michael@kjorling.se \
/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).