From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fun with rc
Date: Thu, 12 Mar 2015 11:31:56 -0700 [thread overview]
Message-ID: <8f5dfd6efd10db2527b518cc0eccc85f@brasstown.quanstro.net> (raw)
In-Reply-To: <87pp8e9jgh.fsf@gmail.com>
On Thu Mar 12 11:10:17 PDT 2015, chneukirchen@gmail.com wrote:
> erik quanstrom <quanstro@quanstro.net> writes:
>
> > so an interesting problem i run into from time to time is separately computing
> > the files added to and deleted from a directory in a shell script. uniq doesn't
> > work for this. certainly one can loop over two lists of files and do
> > this easily,
> > but that seems dull and tedious.
>
> Isn't this a canonical use case for comm(1)?
yes. i hadn't thought of that. that's trivial.
- erik
prev parent reply other threads:[~2015-03-12 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 16:46 erik quanstrom
2015-03-12 17:07 ` minux
2015-03-12 17:17 ` erik quanstrom
2015-03-12 18:09 ` Christian Neukirchen
2015-03-12 18:31 ` erik quanstrom [this message]
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=8f5dfd6efd10db2527b518cc0eccc85f@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).