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

Filename error with unexpected escape in --exec on Windows #722

Open
TroyDanielFZ opened this issue Feb 1, 2021 · 4 comments
Open

Filename error with unexpected escape in --exec on Windows #722

TroyDanielFZ opened this issue Feb 1, 2021 · 4 comments

Comments

@TroyDanielFZ
Copy link

When use the --exec command on windows, the {} isn't properly replaced for files start with rvbt etc under folders.
The expected result is:

folder\thread.txt
folder\var.txt

while the actaul reslt is:

folder^thread.txt
folder^Kar.txt

where the ^t and ^K are control keycodes.

@evanjs
Copy link

evanjs commented Feb 2, 2021

This isn't the same thing as #310, is it?
If it is, try using e.g. fd -x <command> "{}" as mentioned here.

@TroyDanielFZ
Copy link
Author

@evanjs
Thank you for your comment.
After tring the solution provided in #310, this problem is resovled.
It is possibly the same problem as #310 .

1 similar comment
@TroyDanielFZ
Copy link
Author

@evanjs
Thank you for your comment.
After tring the solution provided in #310, this problem is resovled.
It is possibly the same problem as #310 .

@sharkdp
Copy link
Owner

sharkdp commented Feb 13, 2021

@TroyDanielFZ Thank you for reporting this, and thanks for resolving it @evanjs.

It feels like something that should be documented. Maybe we could modify the help text on Windows to add a remark about needing to quote {}?

By the way: note that you can always skip a trailing {} argument. fd … -x cmd is equivalent to fd … -x cmd "{}".

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

No branches or pull requests

3 participants