zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-users@zsh.org>
Subject: Re: find duplicate files
Date: Mon, 8 Apr 2019 16:24:15 +0100	[thread overview]
Message-ID: <1554737055.5822.14.camel@samsung.com> (raw)
In-Reply-To: <391277a7-d604-4c20-a666-a2886b1d2939@eastlink.ca>

On Mon, 2019-04-08 at 07:58 -0700, Ray Andrews wrote:
> Pardon a comment from the peanut gallery, but it seems strange to me 
> that the issue of duplicate files would be something that would not have 
> been solved definitively  50 years ago.  I'd have thought that for 
> donkey's years there would be utilities that would let you find 
> duplicates at various levels of rigour because it's so obviously an 
> issue that's bound to come up.  No?

Slightly philosophical answer.  (The right answer is probably that
actually there are such utilities but a lot of us don't know them.)
Nothing really to do with zsh.

One of the answers may be the way issues of this kind typically arise.
For example: you've copied a whole pile of files somewhere else to
rationalise an interface, or make a new project, or something like
that.  Then the problem isn't so much looking for individual files that
happen to be the same as looking for a bunch of stuff that got copied
together and could really be re-rationalised to avoid the copy.  But
often it's a modified copy so the files are similar but not quite the
same.

On the other hand, if you're looking not for piles of stuff that got
copied but shouldn't, but individual files that happen to be the same,
then you're quite likely to get lots of false positives with e.g.  files
based on a template that are logically different in the sense they are
generated with different arguments but happen to turn out the same
(that's just one random example off the top of my head) and you probably
wouldn't want to rationalise them down to one.

So the use case here maybe isn't quite as common as you might think.

pws



  parent reply	other threads:[~2019-04-08 15:25 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 [this message]
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
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=1554737055.5822.14.camel@samsung.com \
    --to=p.stephenson@samsung.com \
    --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).