find exec '{}' not available after >
Exec allows us to either pass all arguments at once with {} +
or to pass them one by one with {} ;
Now let's say I want to rename all jpeg, no problem doing this:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec mv '{}' '{}'.new ;
But if I need to redirect output, '{}'
isn't accessible after redirection.
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec cjpeg -quality 80 '{}' > optimized_'{}' ;
This wouldn't work. I'd have to use a for loop, storing find's output into a variable before using it. Let's admit it, it's cumbersome.
for f in `find . ( -name '*.jpg' -o -name '*.jpeg' )`; do cjpeg -quality 80 $f > optimized_$f; done;
So is there a better way?
bash find
|
show 4 more comments
Exec allows us to either pass all arguments at once with {} +
or to pass them one by one with {} ;
Now let's say I want to rename all jpeg, no problem doing this:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec mv '{}' '{}'.new ;
But if I need to redirect output, '{}'
isn't accessible after redirection.
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec cjpeg -quality 80 '{}' > optimized_'{}' ;
This wouldn't work. I'd have to use a for loop, storing find's output into a variable before using it. Let's admit it, it's cumbersome.
for f in `find . ( -name '*.jpg' -o -name '*.jpeg' )`; do cjpeg -quality 80 $f > optimized_$f; done;
So is there a better way?
bash find
Isn't there a>
missing in the third code sample?
– choroba
Nov 14 '18 at 11:49
1
Even your first line is nonstandard and thus non-portable. Try to avoid command lines where{}
appears in a longer strings as such strings are typically not expanded.
– schily
Nov 14 '18 at 12:35
That first example does not do what you say.
– ctrl-alt-delor
Nov 14 '18 at 13:05
1
You have fixed your question: I would no-longer change it.
– ctrl-alt-delor
Nov 14 '18 at 13:32
1
For what it's worth, the primary reason that your redirection does not work as you wanted is that it is handled by the shell from which you launchfind
, once, and applied to thefind
command itself. The{}
has no special meaning in that context. The redirection is not an argument tofind
, and it certainly is not part of the-exec
clause.
– John Bollinger
Nov 14 '18 at 19:30
|
show 4 more comments
Exec allows us to either pass all arguments at once with {} +
or to pass them one by one with {} ;
Now let's say I want to rename all jpeg, no problem doing this:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec mv '{}' '{}'.new ;
But if I need to redirect output, '{}'
isn't accessible after redirection.
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec cjpeg -quality 80 '{}' > optimized_'{}' ;
This wouldn't work. I'd have to use a for loop, storing find's output into a variable before using it. Let's admit it, it's cumbersome.
for f in `find . ( -name '*.jpg' -o -name '*.jpeg' )`; do cjpeg -quality 80 $f > optimized_$f; done;
So is there a better way?
bash find
Exec allows us to either pass all arguments at once with {} +
or to pass them one by one with {} ;
Now let's say I want to rename all jpeg, no problem doing this:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec mv '{}' '{}'.new ;
But if I need to redirect output, '{}'
isn't accessible after redirection.
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec cjpeg -quality 80 '{}' > optimized_'{}' ;
This wouldn't work. I'd have to use a for loop, storing find's output into a variable before using it. Let's admit it, it's cumbersome.
for f in `find . ( -name '*.jpg' -o -name '*.jpeg' )`; do cjpeg -quality 80 $f > optimized_$f; done;
So is there a better way?
bash find
bash find
edited Nov 14 '18 at 13:27
Buzut
asked Nov 14 '18 at 11:39
BuzutBuzut
1385
1385
Isn't there a>
missing in the third code sample?
– choroba
Nov 14 '18 at 11:49
1
Even your first line is nonstandard and thus non-portable. Try to avoid command lines where{}
appears in a longer strings as such strings are typically not expanded.
– schily
Nov 14 '18 at 12:35
That first example does not do what you say.
– ctrl-alt-delor
Nov 14 '18 at 13:05
1
You have fixed your question: I would no-longer change it.
– ctrl-alt-delor
Nov 14 '18 at 13:32
1
For what it's worth, the primary reason that your redirection does not work as you wanted is that it is handled by the shell from which you launchfind
, once, and applied to thefind
command itself. The{}
has no special meaning in that context. The redirection is not an argument tofind
, and it certainly is not part of the-exec
clause.
– John Bollinger
Nov 14 '18 at 19:30
|
show 4 more comments
Isn't there a>
missing in the third code sample?
– choroba
Nov 14 '18 at 11:49
1
Even your first line is nonstandard and thus non-portable. Try to avoid command lines where{}
appears in a longer strings as such strings are typically not expanded.
– schily
Nov 14 '18 at 12:35
That first example does not do what you say.
– ctrl-alt-delor
Nov 14 '18 at 13:05
1
You have fixed your question: I would no-longer change it.
– ctrl-alt-delor
Nov 14 '18 at 13:32
1
For what it's worth, the primary reason that your redirection does not work as you wanted is that it is handled by the shell from which you launchfind
, once, and applied to thefind
command itself. The{}
has no special meaning in that context. The redirection is not an argument tofind
, and it certainly is not part of the-exec
clause.
– John Bollinger
Nov 14 '18 at 19:30
Isn't there a
>
missing in the third code sample?– choroba
Nov 14 '18 at 11:49
Isn't there a
>
missing in the third code sample?– choroba
Nov 14 '18 at 11:49
1
1
Even your first line is nonstandard and thus non-portable. Try to avoid command lines where
{}
appears in a longer strings as such strings are typically not expanded.– schily
Nov 14 '18 at 12:35
Even your first line is nonstandard and thus non-portable. Try to avoid command lines where
{}
appears in a longer strings as such strings are typically not expanded.– schily
Nov 14 '18 at 12:35
That first example does not do what you say.
– ctrl-alt-delor
Nov 14 '18 at 13:05
That first example does not do what you say.
– ctrl-alt-delor
Nov 14 '18 at 13:05
1
1
You have fixed your question: I would no-longer change it.
– ctrl-alt-delor
Nov 14 '18 at 13:32
You have fixed your question: I would no-longer change it.
– ctrl-alt-delor
Nov 14 '18 at 13:32
1
1
For what it's worth, the primary reason that your redirection does not work as you wanted is that it is handled by the shell from which you launch
find
, once, and applied to the find
command itself. The {}
has no special meaning in that context. The redirection is not an argument to find
, and it certainly is not part of the -exec
clause.– John Bollinger
Nov 14 '18 at 19:30
For what it's worth, the primary reason that your redirection does not work as you wanted is that it is handled by the shell from which you launch
find
, once, and applied to the find
command itself. The {}
has no special meaning in that context. The redirection is not an argument to find
, and it certainly is not part of the -exec
clause.– John Bollinger
Nov 14 '18 at 19:30
|
show 4 more comments
5 Answers
5
active
oldest
votes
You could use bash -c
within the find -exec
command and use the positional parameter with the bash command:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec bash -c 'cjpeg -quality 80 "$1" > "$(dirname "$1")/optimized_$(basename "$1")"' sh {} ;
That way {}
is provided with $1
.
The sh
before the {}
tells the inner shell its "name", the string used here is used in e.g. error messages. This is discussed more in this answer on stackoverflow.
add a comment |
You have an answer(https://unix.stackexchange.com/a/481687/4778), but here is why.
The redirection >
, and also pipes |
, and $
expansion, are all done by the shell before the command is executed. Therefore stdout is redirected to optimized_{}
, before find
is started.
add a comment |
The redirection needs to be quoted to avoid that the present shell interprets it.
But quoting it will also avoid the output of the command to be redirected.
The known solution to this is to call a shell:
find . -name '*.jpg' -exec sh -c 'echo "$1" >"$1".new' called_shell '{}' ;
In this case, the redirection (>
) is quoted on the present shell and works correctly inside the called shell. The called_shell
is used as the $0
parameter (the name) of the child shell (sh
).
That works well if a suffix is added the name of the file, but not if you use a prefix. For a prefix to work you need both to remove the ./
that find prepend to filenames with ${1#./}
and to use the -execdir
option.
You may (or may not) want to use the -iname
option so that files named *.JPG
or *.JpG
or other variations are also included.
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
cjpeg -quality 80 "$1" > optimized_"${1#./}"
' called_shell '{}' ;
And, you may (or may not) also want to call the shell once per directory instead of once per file by adding a loop (for f do … ; done
) and a +
at the end:
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
for f; do cjpeg -quality 80 "$f" > optimized_"${f#./}"; done
' called_shell '{}' +
And, finally, as cjpeg
is able to directly write to a file, the redirection could be avoided as:
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
for f; do cjpeg -quality 80 "$f" -outfile optimized_"${f#./}"; done
' called_shell '{}' +
add a comment |
cjpeg
has an option that lets you write to a named file, rather than standard output. If your version of find
supports the -execdir
option, you can take advantage of that to make the redirection unnecessary.
find . ( -name '*.jpg' -o -name '*.jpeg' )
-execdir cjpeg -quality 80 -outfile optimized_'{}' '{}' ;
Note: this actually assumes the BSD version of find
, which appears to strip the leading ./
from the file name when exanding to {}
. (Or conversely, GNU find
adds ./
to the name. There's no standard to say which behavior is "right".)
If yourfind
supports-execdir
, you can use that instead of-exec
. It causes the command to run in the directory where the file was found, and{}
will becomeaa.jpg
instead of./t2/aa.jpg
.
– chepner
Nov 14 '18 at 15:33
Still in error:cjpeg: can't open optimized_./aa.jpg
.
– Isaac
Nov 14 '18 at 15:36
Hm, that appears to be a difference between GNUfind
and BSDfind
. (The perils of using non-standard extensions.)
– chepner
Nov 14 '18 at 15:37
A filename without a leading./
seems to be more prone to errors. A reasonable solution is proposed in this answer.
– Isaac
Nov 14 '18 at 15:50
add a comment |
Create a script cjq80:
#!/bin/bash
cjpeg -quality 80 "$1" > "${1%/*}"/optimized_"${1##*/}"
Make it executable
chmod u+x cjq80
And use it in -exec:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec cjq80 '{}' ;
I had though about this, but it's not very handy. Especially as I had to incorporate this in a build process
– Buzut
Nov 14 '18 at 13:25
Just add the script to other build scripts, I find it more readable than doubly nested bash -c.
– choroba
Nov 14 '18 at 13:57
Well, it's a matter of taste. Now every option is specified so if someone encounters the same issue, he'll choose for himself :)
– Buzut
Nov 14 '18 at 14:37
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481685%2ffind-exec-not-available-after%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
You could use bash -c
within the find -exec
command and use the positional parameter with the bash command:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec bash -c 'cjpeg -quality 80 "$1" > "$(dirname "$1")/optimized_$(basename "$1")"' sh {} ;
That way {}
is provided with $1
.
The sh
before the {}
tells the inner shell its "name", the string used here is used in e.g. error messages. This is discussed more in this answer on stackoverflow.
add a comment |
You could use bash -c
within the find -exec
command and use the positional parameter with the bash command:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec bash -c 'cjpeg -quality 80 "$1" > "$(dirname "$1")/optimized_$(basename "$1")"' sh {} ;
That way {}
is provided with $1
.
The sh
before the {}
tells the inner shell its "name", the string used here is used in e.g. error messages. This is discussed more in this answer on stackoverflow.
add a comment |
You could use bash -c
within the find -exec
command and use the positional parameter with the bash command:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec bash -c 'cjpeg -quality 80 "$1" > "$(dirname "$1")/optimized_$(basename "$1")"' sh {} ;
That way {}
is provided with $1
.
The sh
before the {}
tells the inner shell its "name", the string used here is used in e.g. error messages. This is discussed more in this answer on stackoverflow.
You could use bash -c
within the find -exec
command and use the positional parameter with the bash command:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec bash -c 'cjpeg -quality 80 "$1" > "$(dirname "$1")/optimized_$(basename "$1")"' sh {} ;
That way {}
is provided with $1
.
The sh
before the {}
tells the inner shell its "name", the string used here is used in e.g. error messages. This is discussed more in this answer on stackoverflow.
edited Nov 14 '18 at 18:04
answered Nov 14 '18 at 11:49
olivoliv
1,651311
1,651311
add a comment |
add a comment |
You have an answer(https://unix.stackexchange.com/a/481687/4778), but here is why.
The redirection >
, and also pipes |
, and $
expansion, are all done by the shell before the command is executed. Therefore stdout is redirected to optimized_{}
, before find
is started.
add a comment |
You have an answer(https://unix.stackexchange.com/a/481687/4778), but here is why.
The redirection >
, and also pipes |
, and $
expansion, are all done by the shell before the command is executed. Therefore stdout is redirected to optimized_{}
, before find
is started.
add a comment |
You have an answer(https://unix.stackexchange.com/a/481687/4778), but here is why.
The redirection >
, and also pipes |
, and $
expansion, are all done by the shell before the command is executed. Therefore stdout is redirected to optimized_{}
, before find
is started.
You have an answer(https://unix.stackexchange.com/a/481687/4778), but here is why.
The redirection >
, and also pipes |
, and $
expansion, are all done by the shell before the command is executed. Therefore stdout is redirected to optimized_{}
, before find
is started.
answered Nov 14 '18 at 13:09
ctrl-alt-delorctrl-alt-delor
11.5k42059
11.5k42059
add a comment |
add a comment |
The redirection needs to be quoted to avoid that the present shell interprets it.
But quoting it will also avoid the output of the command to be redirected.
The known solution to this is to call a shell:
find . -name '*.jpg' -exec sh -c 'echo "$1" >"$1".new' called_shell '{}' ;
In this case, the redirection (>
) is quoted on the present shell and works correctly inside the called shell. The called_shell
is used as the $0
parameter (the name) of the child shell (sh
).
That works well if a suffix is added the name of the file, but not if you use a prefix. For a prefix to work you need both to remove the ./
that find prepend to filenames with ${1#./}
and to use the -execdir
option.
You may (or may not) want to use the -iname
option so that files named *.JPG
or *.JpG
or other variations are also included.
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
cjpeg -quality 80 "$1" > optimized_"${1#./}"
' called_shell '{}' ;
And, you may (or may not) also want to call the shell once per directory instead of once per file by adding a loop (for f do … ; done
) and a +
at the end:
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
for f; do cjpeg -quality 80 "$f" > optimized_"${f#./}"; done
' called_shell '{}' +
And, finally, as cjpeg
is able to directly write to a file, the redirection could be avoided as:
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
for f; do cjpeg -quality 80 "$f" -outfile optimized_"${f#./}"; done
' called_shell '{}' +
add a comment |
The redirection needs to be quoted to avoid that the present shell interprets it.
But quoting it will also avoid the output of the command to be redirected.
The known solution to this is to call a shell:
find . -name '*.jpg' -exec sh -c 'echo "$1" >"$1".new' called_shell '{}' ;
In this case, the redirection (>
) is quoted on the present shell and works correctly inside the called shell. The called_shell
is used as the $0
parameter (the name) of the child shell (sh
).
That works well if a suffix is added the name of the file, but not if you use a prefix. For a prefix to work you need both to remove the ./
that find prepend to filenames with ${1#./}
and to use the -execdir
option.
You may (or may not) want to use the -iname
option so that files named *.JPG
or *.JpG
or other variations are also included.
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
cjpeg -quality 80 "$1" > optimized_"${1#./}"
' called_shell '{}' ;
And, you may (or may not) also want to call the shell once per directory instead of once per file by adding a loop (for f do … ; done
) and a +
at the end:
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
for f; do cjpeg -quality 80 "$f" > optimized_"${f#./}"; done
' called_shell '{}' +
And, finally, as cjpeg
is able to directly write to a file, the redirection could be avoided as:
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
for f; do cjpeg -quality 80 "$f" -outfile optimized_"${f#./}"; done
' called_shell '{}' +
add a comment |
The redirection needs to be quoted to avoid that the present shell interprets it.
But quoting it will also avoid the output of the command to be redirected.
The known solution to this is to call a shell:
find . -name '*.jpg' -exec sh -c 'echo "$1" >"$1".new' called_shell '{}' ;
In this case, the redirection (>
) is quoted on the present shell and works correctly inside the called shell. The called_shell
is used as the $0
parameter (the name) of the child shell (sh
).
That works well if a suffix is added the name of the file, but not if you use a prefix. For a prefix to work you need both to remove the ./
that find prepend to filenames with ${1#./}
and to use the -execdir
option.
You may (or may not) want to use the -iname
option so that files named *.JPG
or *.JpG
or other variations are also included.
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
cjpeg -quality 80 "$1" > optimized_"${1#./}"
' called_shell '{}' ;
And, you may (or may not) also want to call the shell once per directory instead of once per file by adding a loop (for f do … ; done
) and a +
at the end:
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
for f; do cjpeg -quality 80 "$f" > optimized_"${f#./}"; done
' called_shell '{}' +
And, finally, as cjpeg
is able to directly write to a file, the redirection could be avoided as:
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
for f; do cjpeg -quality 80 "$f" -outfile optimized_"${f#./}"; done
' called_shell '{}' +
The redirection needs to be quoted to avoid that the present shell interprets it.
But quoting it will also avoid the output of the command to be redirected.
The known solution to this is to call a shell:
find . -name '*.jpg' -exec sh -c 'echo "$1" >"$1".new' called_shell '{}' ;
In this case, the redirection (>
) is quoted on the present shell and works correctly inside the called shell. The called_shell
is used as the $0
parameter (the name) of the child shell (sh
).
That works well if a suffix is added the name of the file, but not if you use a prefix. For a prefix to work you need both to remove the ./
that find prepend to filenames with ${1#./}
and to use the -execdir
option.
You may (or may not) want to use the -iname
option so that files named *.JPG
or *.JpG
or other variations are also included.
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
cjpeg -quality 80 "$1" > optimized_"${1#./}"
' called_shell '{}' ;
And, you may (or may not) also want to call the shell once per directory instead of once per file by adding a loop (for f do … ; done
) and a +
at the end:
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
for f; do cjpeg -quality 80 "$f" > optimized_"${f#./}"; done
' called_shell '{}' +
And, finally, as cjpeg
is able to directly write to a file, the redirection could be avoided as:
find . ( -iname '*.jpg' -o -iname '*.jpeg' ) -execdir sh -c '
for f; do cjpeg -quality 80 "$f" -outfile optimized_"${f#./}"; done
' called_shell '{}' +
edited Nov 14 '18 at 15:30
answered Nov 14 '18 at 15:23
IsaacIsaac
11.9k11852
11.9k11852
add a comment |
add a comment |
cjpeg
has an option that lets you write to a named file, rather than standard output. If your version of find
supports the -execdir
option, you can take advantage of that to make the redirection unnecessary.
find . ( -name '*.jpg' -o -name '*.jpeg' )
-execdir cjpeg -quality 80 -outfile optimized_'{}' '{}' ;
Note: this actually assumes the BSD version of find
, which appears to strip the leading ./
from the file name when exanding to {}
. (Or conversely, GNU find
adds ./
to the name. There's no standard to say which behavior is "right".)
If yourfind
supports-execdir
, you can use that instead of-exec
. It causes the command to run in the directory where the file was found, and{}
will becomeaa.jpg
instead of./t2/aa.jpg
.
– chepner
Nov 14 '18 at 15:33
Still in error:cjpeg: can't open optimized_./aa.jpg
.
– Isaac
Nov 14 '18 at 15:36
Hm, that appears to be a difference between GNUfind
and BSDfind
. (The perils of using non-standard extensions.)
– chepner
Nov 14 '18 at 15:37
A filename without a leading./
seems to be more prone to errors. A reasonable solution is proposed in this answer.
– Isaac
Nov 14 '18 at 15:50
add a comment |
cjpeg
has an option that lets you write to a named file, rather than standard output. If your version of find
supports the -execdir
option, you can take advantage of that to make the redirection unnecessary.
find . ( -name '*.jpg' -o -name '*.jpeg' )
-execdir cjpeg -quality 80 -outfile optimized_'{}' '{}' ;
Note: this actually assumes the BSD version of find
, which appears to strip the leading ./
from the file name when exanding to {}
. (Or conversely, GNU find
adds ./
to the name. There's no standard to say which behavior is "right".)
If yourfind
supports-execdir
, you can use that instead of-exec
. It causes the command to run in the directory where the file was found, and{}
will becomeaa.jpg
instead of./t2/aa.jpg
.
– chepner
Nov 14 '18 at 15:33
Still in error:cjpeg: can't open optimized_./aa.jpg
.
– Isaac
Nov 14 '18 at 15:36
Hm, that appears to be a difference between GNUfind
and BSDfind
. (The perils of using non-standard extensions.)
– chepner
Nov 14 '18 at 15:37
A filename without a leading./
seems to be more prone to errors. A reasonable solution is proposed in this answer.
– Isaac
Nov 14 '18 at 15:50
add a comment |
cjpeg
has an option that lets you write to a named file, rather than standard output. If your version of find
supports the -execdir
option, you can take advantage of that to make the redirection unnecessary.
find . ( -name '*.jpg' -o -name '*.jpeg' )
-execdir cjpeg -quality 80 -outfile optimized_'{}' '{}' ;
Note: this actually assumes the BSD version of find
, which appears to strip the leading ./
from the file name when exanding to {}
. (Or conversely, GNU find
adds ./
to the name. There's no standard to say which behavior is "right".)
cjpeg
has an option that lets you write to a named file, rather than standard output. If your version of find
supports the -execdir
option, you can take advantage of that to make the redirection unnecessary.
find . ( -name '*.jpg' -o -name '*.jpeg' )
-execdir cjpeg -quality 80 -outfile optimized_'{}' '{}' ;
Note: this actually assumes the BSD version of find
, which appears to strip the leading ./
from the file name when exanding to {}
. (Or conversely, GNU find
adds ./
to the name. There's no standard to say which behavior is "right".)
edited Nov 14 '18 at 15:43
answered Nov 14 '18 at 14:55
chepnerchepner
5,3501423
5,3501423
If yourfind
supports-execdir
, you can use that instead of-exec
. It causes the command to run in the directory where the file was found, and{}
will becomeaa.jpg
instead of./t2/aa.jpg
.
– chepner
Nov 14 '18 at 15:33
Still in error:cjpeg: can't open optimized_./aa.jpg
.
– Isaac
Nov 14 '18 at 15:36
Hm, that appears to be a difference between GNUfind
and BSDfind
. (The perils of using non-standard extensions.)
– chepner
Nov 14 '18 at 15:37
A filename without a leading./
seems to be more prone to errors. A reasonable solution is proposed in this answer.
– Isaac
Nov 14 '18 at 15:50
add a comment |
If yourfind
supports-execdir
, you can use that instead of-exec
. It causes the command to run in the directory where the file was found, and{}
will becomeaa.jpg
instead of./t2/aa.jpg
.
– chepner
Nov 14 '18 at 15:33
Still in error:cjpeg: can't open optimized_./aa.jpg
.
– Isaac
Nov 14 '18 at 15:36
Hm, that appears to be a difference between GNUfind
and BSDfind
. (The perils of using non-standard extensions.)
– chepner
Nov 14 '18 at 15:37
A filename without a leading./
seems to be more prone to errors. A reasonable solution is proposed in this answer.
– Isaac
Nov 14 '18 at 15:50
If your
find
supports -execdir
, you can use that instead of -exec
. It causes the command to run in the directory where the file was found, and {}
will become aa.jpg
instead of ./t2/aa.jpg
.– chepner
Nov 14 '18 at 15:33
If your
find
supports -execdir
, you can use that instead of -exec
. It causes the command to run in the directory where the file was found, and {}
will become aa.jpg
instead of ./t2/aa.jpg
.– chepner
Nov 14 '18 at 15:33
Still in error:
cjpeg: can't open optimized_./aa.jpg
.– Isaac
Nov 14 '18 at 15:36
Still in error:
cjpeg: can't open optimized_./aa.jpg
.– Isaac
Nov 14 '18 at 15:36
Hm, that appears to be a difference between GNU
find
and BSD find
. (The perils of using non-standard extensions.)– chepner
Nov 14 '18 at 15:37
Hm, that appears to be a difference between GNU
find
and BSD find
. (The perils of using non-standard extensions.)– chepner
Nov 14 '18 at 15:37
A filename without a leading
./
seems to be more prone to errors. A reasonable solution is proposed in this answer.– Isaac
Nov 14 '18 at 15:50
A filename without a leading
./
seems to be more prone to errors. A reasonable solution is proposed in this answer.– Isaac
Nov 14 '18 at 15:50
add a comment |
Create a script cjq80:
#!/bin/bash
cjpeg -quality 80 "$1" > "${1%/*}"/optimized_"${1##*/}"
Make it executable
chmod u+x cjq80
And use it in -exec:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec cjq80 '{}' ;
I had though about this, but it's not very handy. Especially as I had to incorporate this in a build process
– Buzut
Nov 14 '18 at 13:25
Just add the script to other build scripts, I find it more readable than doubly nested bash -c.
– choroba
Nov 14 '18 at 13:57
Well, it's a matter of taste. Now every option is specified so if someone encounters the same issue, he'll choose for himself :)
– Buzut
Nov 14 '18 at 14:37
add a comment |
Create a script cjq80:
#!/bin/bash
cjpeg -quality 80 "$1" > "${1%/*}"/optimized_"${1##*/}"
Make it executable
chmod u+x cjq80
And use it in -exec:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec cjq80 '{}' ;
I had though about this, but it's not very handy. Especially as I had to incorporate this in a build process
– Buzut
Nov 14 '18 at 13:25
Just add the script to other build scripts, I find it more readable than doubly nested bash -c.
– choroba
Nov 14 '18 at 13:57
Well, it's a matter of taste. Now every option is specified so if someone encounters the same issue, he'll choose for himself :)
– Buzut
Nov 14 '18 at 14:37
add a comment |
Create a script cjq80:
#!/bin/bash
cjpeg -quality 80 "$1" > "${1%/*}"/optimized_"${1##*/}"
Make it executable
chmod u+x cjq80
And use it in -exec:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec cjq80 '{}' ;
Create a script cjq80:
#!/bin/bash
cjpeg -quality 80 "$1" > "${1%/*}"/optimized_"${1##*/}"
Make it executable
chmod u+x cjq80
And use it in -exec:
find . ( -name '*.jpg' -o -name '*.jpeg' ) -exec cjq80 '{}' ;
edited Nov 15 '18 at 20:47
answered Nov 14 '18 at 11:51
chorobachoroba
26.6k44975
26.6k44975
I had though about this, but it's not very handy. Especially as I had to incorporate this in a build process
– Buzut
Nov 14 '18 at 13:25
Just add the script to other build scripts, I find it more readable than doubly nested bash -c.
– choroba
Nov 14 '18 at 13:57
Well, it's a matter of taste. Now every option is specified so if someone encounters the same issue, he'll choose for himself :)
– Buzut
Nov 14 '18 at 14:37
add a comment |
I had though about this, but it's not very handy. Especially as I had to incorporate this in a build process
– Buzut
Nov 14 '18 at 13:25
Just add the script to other build scripts, I find it more readable than doubly nested bash -c.
– choroba
Nov 14 '18 at 13:57
Well, it's a matter of taste. Now every option is specified so if someone encounters the same issue, he'll choose for himself :)
– Buzut
Nov 14 '18 at 14:37
I had though about this, but it's not very handy. Especially as I had to incorporate this in a build process
– Buzut
Nov 14 '18 at 13:25
I had though about this, but it's not very handy. Especially as I had to incorporate this in a build process
– Buzut
Nov 14 '18 at 13:25
Just add the script to other build scripts, I find it more readable than doubly nested bash -c.
– choroba
Nov 14 '18 at 13:57
Just add the script to other build scripts, I find it more readable than doubly nested bash -c.
– choroba
Nov 14 '18 at 13:57
Well, it's a matter of taste. Now every option is specified so if someone encounters the same issue, he'll choose for himself :)
– Buzut
Nov 14 '18 at 14:37
Well, it's a matter of taste. Now every option is specified so if someone encounters the same issue, he'll choose for himself :)
– Buzut
Nov 14 '18 at 14:37
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481685%2ffind-exec-not-available-after%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Isn't there a
>
missing in the third code sample?– choroba
Nov 14 '18 at 11:49
1
Even your first line is nonstandard and thus non-portable. Try to avoid command lines where
{}
appears in a longer strings as such strings are typically not expanded.– schily
Nov 14 '18 at 12:35
That first example does not do what you say.
– ctrl-alt-delor
Nov 14 '18 at 13:05
1
You have fixed your question: I would no-longer change it.
– ctrl-alt-delor
Nov 14 '18 at 13:32
1
For what it's worth, the primary reason that your redirection does not work as you wanted is that it is handled by the shell from which you launch
find
, once, and applied to thefind
command itself. The{}
has no special meaning in that context. The redirection is not an argument tofind
, and it certainly is not part of the-exec
clause.– John Bollinger
Nov 14 '18 at 19:30