From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: find duplicate files
Date: Mon, 8 Apr 2019 18:28:54 -0700 [thread overview]
Message-ID: <e1f2d799-4411-1a85-6815-84e2d2271da1@eastlink.ca> (raw)
In-Reply-To: <ufamul0c7f0.fsf@epithumia.math.uh.edu>
On 2019-04-08 6:08 p.m., Jason L Tibbitts III wrote:
>
> RA> I'd have thought that for donkey's years there would be utilities
> RA> that would let you find duplicates at various levels of rigour
> RA> because it's so obviously an issue that's bound to come up.
>
> What makes you think that such utilities don't exist?
I thought that they do exist, and many have been named.
> The fact that
> people discuss pure zsh ways to do something doesn't say much about
> whether non-zsh things exist.
Sure, as an exercise or some customization, but in this case it seemed
like there was a genuine need, but the problem didn't seem exotic so I
thought I'd ask. Looks to me like an official 'zdupe' is in order and
90% already cooked.
>
> For example, I've used "duff" for this. http://duff.dreda.org/
What a fine document. But why is so much computer documentation so
bloody awful?
next prev parent reply other threads:[~2019-04-09 1:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 5:40 Emanuel Berg
2019-04-06 13:02 ` Paul Hoffman
2019-04-06 14:44 ` Emanuel Berg
2019-04-06 19:11 ` zv
2019-04-06 19:42 ` Emanuel Berg
2019-04-08 14:37 ` Paul Hoffman
2019-04-08 14:58 ` Ray Andrews
2019-04-08 15:14 ` Volodymyr Khomchak
2019-04-08 15:24 ` Peter Stephenson
2019-04-08 15:32 ` Andrew J. Rech
2019-04-08 15:47 ` Oliver Kiddle
2019-04-08 16:29 ` Ray Andrews
2019-04-08 16:45 ` Bart Schaefer
2019-04-08 21:30 ` Emanuel Berg
2019-04-09 1:08 ` Jason L Tibbitts III
2019-04-09 1:28 ` Ray Andrews [this message]
2019-04-09 9:28 ` Charles Blake
2019-04-08 21:26 ` Emanuel Berg
2019-04-07 11:16 ` Charles Blake
2019-04-07 21:32 ` Bart Schaefer
2019-04-08 11:17 ` Charles Blake
2019-04-08 17:14 ` Bart Schaefer
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=e1f2d799-4411-1a85-6815-84e2d2271da1@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).