Skip to content
This repository was archived by the owner on Nov 22, 2022. It is now read-only.
This repository was archived by the owner on Nov 22, 2022. It is now read-only.

chaining exclusions results in no files being excluded #22

Description

@lahwran

eg. given this setup:

# install current release version as of this issue
curl -Ls https://github.com/amoffat/supertag/releases/download/v0.1.4/supertag-x86_64.AppImage > /tmp/tag-0.1.4
chmod +x /tmp/tag-0.1.4
function tag() { /tmp/tag-0.1.4 "$@"; }

# make a debug collection
cd /mnt # change to your base (mine is ~)
sudo mkdir -p supertagdebug
sudo chown $USER:$USER supertagdebug
tag mount supertagdebug
cd supertagdebug

this test case fails:

touch /tmp/{a1,a2,ab,b1,b2,c1}
tag ln /tmp/{a1,a2,ab,b1,b2,c} $PWD/basetag/
tag ln /tmp/{a1,a2,ab} $PWD/basetag/a
tag ln /tmp/{ab,b1,b2} $PWD/basetag/b
tag ln /tmp/c1 $PWD/basetag/c

echo "actual:"
ls basetag/-a/-b/_/
echo "actual vs expected:"
diff <(ls basetag/-a/-b/_/) - << EXPECTED
c1
EXPECTED
echo "actual vs no filtering:"
diff <(ls basetag/-a/-b/_/) <(ls basetag/_/)

I get the output:

actual:
a1
a2
b1
b2
c1
actual vs expected:
1,4d0
< a1
< a2
< b1
< b2
actual vs no filtering:
2a3
> ab

it seems to be excluding the intersection of the intersected tags, rather than individually excluding each separate exclude tag.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions