[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #18466] -execdir {} + broken in new find
From: |
Eric Blake |
Subject: |
[bug #18466] -execdir {} + broken in new find |
Date: |
Wed, 06 Dec 2006 04:29:06 +0000 |
User-agent: |
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1) |
URL:
<http://savannah.gnu.org/bugs/?18466>
Summary: -execdir {} + broken in new find
Project: findutils
Submitted by: ericb
Submitted on: Tuesday 12/05/2006 at 21:29
Category: find
Severity: 4 - Important
Item Group: Wrong result
Status: None
Privacy: Public
Assigned to: None
Originator Name: Eric Blake
Originator Email: address@hidden
Open/Closed: Open
Discussion Lock: Any
Release: 4.3.2
Fixed Release: None
_______________________________________________________
Details:
The change from oldfind to the fts algorithm broke -execdir {} +:
http://cygwin.com/ml/cygwin/2006-12/msg00203.html
The command is being run in the parent directory rather than the directory
that provided the current set of {} argument expansions.
I'm not sure of the fix off hand, but it seems like leaving a directory is
the trigger to run the command on the collected arguments, but it triggers
after the working dir has already been changed. You either need to trigger
sooner, or temporarily revert the working directory back to where the
arguments were collected.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?18466>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #18466] -execdir {} + broken in new find,
Eric Blake <=