Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apply ordering to fclones action --dry-run results #96

Closed
mattalxndr opened this issue Jan 6, 2022 · 0 comments · Fixed by #129
Closed

Apply ordering to fclones action --dry-run results #96

mattalxndr opened this issue Jan 6, 2022 · 0 comments · Fixed by #129
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@mattalxndr
Copy link

I'm running this in order to test that my --priority and --keep-path values are right:

watch 'fclones remove --dry-run < results-file.out'

Unfortunately, it's not working because the results are not ordered. So the command is rerun, and the list items dance around every time watch updates.

I thought maybe concurrency was affecting it, so I tried --threads main:1 but that only seems to apply to the group action and not the others.

My workaround right now is to run the results through | sort but it's not ideal because I need to look for each result in the alphabetical list.

So my feature request is to add some ordering to the result list, preferably in the same order as the input list. Even if the ordering is not exposed in the CLI options in any way, it would be a help.

@pkolaczk pkolaczk added the enhancement New feature or request label Jan 7, 2022
@pkolaczk pkolaczk self-assigned this May 15, 2022
pkolaczk added a commit that referenced this issue May 16, 2022
pkolaczk added a commit that referenced this issue May 16, 2022
pkolaczk added a commit that referenced this issue May 16, 2022
@pkolaczk pkolaczk added this to the 0.25 milestone May 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants