From: Will Senn <will.senn@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] cut, paste, join, etc.
Date: Tue, 16 Feb 2021 15:15:45 -0600 [thread overview]
Message-ID: <b51f3f9e-da9e-c914-c139-b24e2a7bf15c@gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2102170756340.70858@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On 2/16/21 3:02 PM, Dave Horsfall wrote:
> On Tue, 16 Feb 2021, Will Senn wrote:
>
>> 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...
>
> I use "cut" a fair bit, rarely use "paste", but as for "join" and
> RDBs, just look at the man page: "join — relational database
> operator". As for future use, who knows? Could be a fun project for
> someone with time on their hands (not me!).
>
> -- Dave, who once implemented a "join" operation with BDB
Oh brother! RTFM... properly... :). Still, I'm curious about the history.
Will
[-- Attachment #2: Type: text/html, Size: 1434 bytes --]
next prev parent reply other threads:[~2021-02-16 21:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 20:33 Will Senn
2021-02-16 21:02 ` Dave Horsfall
2021-02-16 21:15 ` Will Senn [this message]
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=b51f3f9e-da9e-c914-c139-b24e2a7bf15c@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).