From: Emanuel Berg <moasenwood@zoho.eu>
To: zsh-users@zsh.org
Subject: Re: find duplicate files
Date: Mon, 08 Apr 2019 23:26:23 +0200 [thread overview]
Message-ID: <86v9zour28.fsf@zoho.eu> (raw)
In-Reply-To: <20190408143748.GA21630@trot>
Paul Hoffman wrote:
>> > #!/bin/zsh
>> > find-duplicates () {
>> > (( # > 0 )) || set -- *(.N)
>> > local dups=0
>> > md5sum $@ | sort | awk '{ print $2,$1 }' | uniq -c -f1 | \
>> > grep -v '^ *1 ' | wc -l | read dups
>> > (( dups == 0 )) && echo "no duplicates"
>> > }
>>
>> Still nothing :)
>
> What were you expecting? It exits with status
> 0 if there were no duplicates; otherwise, it
> exits with status 1.
OK! Yes, it works. Thank you. I put your name
next to it in the file [1]. Only I expected it
to tell what files are duplicates. Otherwise it
isn't so useful :)
> # is the name of a variable (a "variable" is
> zsh terminology). Its value is the number of
> positional parameters, i.e., the number of
> elements in $argv. Within (( ... )) you don't
> need the dollar sign before a variable name,
> but (for the most part) it doesn't hurt to
> use it
OK, thanks. Better to use the dollar sign so
that it doesn't brake the font lock and look
like a comment.
[1] http://user.it.uu.se/~embe8573/conf/.zsh/files-fs
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2019-04-08 21:27 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
2019-04-09 9:28 ` Charles Blake
2019-04-08 21:26 ` Emanuel Berg [this message]
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=86v9zour28.fsf@zoho.eu \
--to=moasenwood@zoho.eu \
--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).