From: Will Senn <will.senn@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] cut, paste, join, etc.
Date: Tue, 16 Feb 2021 14:33:05 -0600 [thread overview]
Message-ID: <3987726c-db35-79fc-00cb-5d979cfaf53a@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
All,
I'm tooling along during our newfangled rolling blackouts and frigid
temperatures (in Texas!) and reading some good old unix books. I keep
coming across the commands cut and paste and join and suchlike. I use
cut all the time for stuff like:
ls -l | tr -s ' '| cut -f1,4,9 -d \
...
-rw-r--r-- staff main.rs
and
who | grep wsenn | cut -c 1-8,10-17
wsenn console
wsenn ttys000
but that's just cuz it's convenient and useful.
To my knowledge, I've never used paste or join outside of initially
coming across them. But, they seem to 'fit' with cut. My question for
y'all is, was there a subset of related utilities that these were part
of that served some common purpose? On a related note, join seems like
part of an aborted (aka never fully realized) attempt at a text based
rdb to me...
What say you?
Will
[-- Attachment #2: Type: text/html, Size: 1275 bytes --]
next reply other threads:[~2021-02-16 20:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 20:33 Will Senn [this message]
2021-02-16 21:02 ` Dave Horsfall
2021-02-16 21:15 ` Will Senn
2021-02-16 21:26 ` Dave Horsfall
2021-02-16 21:06 ` Dennis Boone
2021-02-17 1:08 M Douglas McIlroy
2021-02-17 1:16 ` Will Senn
2021-02-17 1:43 ` Grant Taylor via TUHS
2021-02-17 2:26 ` Will Senn
2021-02-17 4:08 ` Grant Taylor via TUHS
2021-02-17 10:14 ` John Gilmore
2021-02-17 14:52 ` Andrew Hume
2021-02-17 23:58 ` Dan Cross
2021-02-17 20:49 ` Dave Horsfall
2021-02-22 5:57 ` Tomasz Rola
2021-02-17 3:29 ` John Cowan
2021-02-18 20:20 Brian Walden
2021-02-18 20:41 ` Anthony Martin
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=3987726c-db35-79fc-00cb-5d979cfaf53a@gmail.com \
--to=will.senn@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).