We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When running exec, single quote inside double quote doesn't seem to work:
$ fd -x echo "hello'world'" helloworld ./b helloworld ./b/file2.txt helloworld ./file.txt
However, it is fine when there's a space in between:
$ fd -x echo "hello 'world'" hello 'world' ./b/file2.txt hello 'world' ./b hello 'world' ./file.txt
Trying to escape with backslash yields weird results:
fd -x echo "hello\'world\'" hello\world' ./file.txt hello\world' ./b hello\world' ./b/file2.txt
I also can not reproduce this bug on Linux.
Using find:
$ find . -exec echo "hello'world'" {} \; hello'world' . hello'world' ./b hello'world' ./b/file2.txt hello'world' ./file.txt
Using gnu parallel:
$ fd | parallel echo "hello\'world\'" hello'world' b/ hello'world' b/file2.txt hello'world' file.txt
fd
fd 10.1.0
$ uname -srm MINGW64_NT-10.0-22631 3.5.3.x86_64 x86_64
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Checks
Describe the bug you encountered:
When running exec, single quote inside double quote doesn't seem to work:
However, it is fine when there's a space in between:
Trying to escape with backslash yields weird results:
I also can not reproduce this bug on Linux.
Describe what you expected to happen:
Using find:
Using gnu parallel:
What version of
fd
are you using?fd 10.1.0
Which operating system / distribution are you on?
The text was updated successfully, but these errors were encountered: