Re: Bugfix: Failure of -execdir to process arguments at depth 0

[Bas van Gompel]

Op Sat, 5 Feb 2005 12:19:55 +0000 schreef James Youngman
in <address@hidden>:
:  On Thu, Feb 03, 2005 at 11:23:26PM +0000, James Youngman wrote:
:
: > I have put in place (in CVS) a quick fix for the problem.  It makes
: > -execdir work the same as -exec when (state.curdepth==0).  The problem
: > is that the working directory at that point will still be the same as
: > it was when we started, as we have not recursed into any directories
: > yet.
: >
: > If you have a good suggestion as to how this should be better solved,
: > please let me know.
:
:  I have now checked into CVS a change which properly resolves the
:  problem, much as described below.

This appears to work well. However when the rootdir is passed,
something looks fishy:

find / -mindepth 0 -maxdepth 0 -execdir echo {} \;
.//

I also spotted, when `+' is used:

find / -mindepth 0 -maxdepth 0 -execdir echo == {} +
==
== .//

(Notice the first line of output, which should not be there.)

[...]


L8r,

Buzz.
-- 
  ) |  | ---/ ---/  Yes, this | This message consists of true | I do not
--  |  |   /    /   really is |   and false bits entirely.    | mail for
  ) |  |  /    /    a 72 by 4 +-------------------------------+ any1 but
--  \--| /--- /---  .sigfile. |   |perl -pe "s.u(z)\1.as."    | me. 4^re