From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: find duplicate files
Date: Mon, 8 Apr 2019 09:45:56 -0700 [thread overview]
Message-ID: <CAH+w=7YPJ72DsrV5-d-FUpdsu9YWMQFQ7Bgk7PgsggWQru=m=A@mail.gmail.com> (raw)
In-Reply-To: <765759fc-cd56-e13b-c346-47041bb63a86@eastlink.ca>
On Mon, Apr 8, 2019 at 9:30 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> So then why do we need a new zsh based solution?
The most typical answer would be that you have a shell and the
standard utilities but not the ability or permission necessary to
install a new specialized utility.
Another answer is that it's an interesting algorithmic question and
demonstrates techniques that could be applied to other problems.
> particularly note what Peter said about files that are logically
> different but coincidentally the same.
Yes, if you run my sample script in an active zsh build tree it will
find a lot of those.
next prev parent reply other threads:[~2019-04-08 16:46 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 [this message]
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='CAH+w=7YPJ72DsrV5-d-FUpdsu9YWMQFQ7Bgk7PgsggWQru=m=A@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=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).