Hi Joey
Thanks for an amazing tool!
I have a minor nitpick regarding git annex list output when using "alternative" git remotes for the same repository.
My use case: I have a several devices which can be accessed either remotely via a ssh jump host, or locally via a 192.168.x.x address (git remotes like deviceN-local, deviceN-remote). This means I have two remotes for every unique repo. As git annex list outputs one column of Xs per remote, this means I have duplicates in there for every device, which causes the list to be very wide and hard to read with more than a couple of remotes (I have 8 unique=16 remotes in one repo).
Would it be possible to get git annex list to (optionally) output one column per unique remote/UUID, e.g. by taking the name of the lowest cost remote with each UUID? This could be behind a flag, e.g. --unique-repos or similar.
Best, KM
I think you would be better off using
git-annex whereisin this kind of situation.--unique-repos would be a fix specific to your own situation of having multiple names for a repo, but it would not help a user who had similar difficulty reading the output just because they have a lot of different repos.
The output of
git-annex whereisis better suited to scaling to a lot of repos.--unique-reposand a configannex.listuniquereposas I have the same setup as OP.git annex listis a very compact view that can't always be swapped for the verbosegit annex whereis.