Re: whats wrong with find -exec sed?
- From: tom <me@xxxxxxxxxx>
- Date: Thu, 02 Nov 2006 15:26:42 +0100
thanks so much. I tried this before, but did not place the space in front of the backslash. I just was lost in possibilities ;-)
But my first command still doesn't do what it is supposed to. files get completly empty now.
I dont care anymore. Made the changes in an texteditor (very anoying)...
But thanks anyway!
Thomas
Sybren Stuvel wrote:
tom enlightened us with:.
it's me again:
this does not work neither:
# find . -iname "*.pl" -exec echo "Hello {}";
find: missing argument to `-exec'
something wrong with find?
Nope, something wrong with the command. Your shell sees ';' as a
command separator. When it sees this:
# cmd a; cmd b
It executes "cmd a" and then "cmd b". As you can see, neither command
actually "see" the ";". Because of this, you need to escape it:
# find . -iname "*.pl" -exec echo "Hello {}" \;
Sybren
- Follow-Ups:
- Re: whats wrong with find -exec sed?
- From: Robert Newson
- Re: whats wrong with find -exec sed?
- References:
- whats wrong with find -exec sed?
- From: tom
- Re: whats wrong with find -exec sed?
- From: tom
- Re: whats wrong with find -exec sed?
- From: Sybren Stuvel
- whats wrong with find -exec sed?
- Prev by Date: Installation of FC6 fails with a kernel panic, probably due to AGP
- Next by Date: Re: Installation of FC6 fails with a kernel panic, probably due to AGP
- Previous by thread: Re: whats wrong with find -exec sed?
- Next by thread: Re: whats wrong with find -exec sed?
- Index(es):
Relevant Pages
|
