[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #18576] -execdir vs. PATH
From: |
Eric Blake |
Subject: |
[bug #18576] -execdir vs. PATH |
Date: |
Wed, 27 Dec 2006 02:54:55 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 Mnenhy/0.7.4.666 |
Follow-up Comment #5, bug #18576 (project findutils):
Yes, -execdir currently fails when . is on PATH, and I don't see any reason
to change that aspect of the behavior, since -execdir is not standardized.
If you relax to just a warning, then by the time a warning is printed, find
would have already forked the problem process. And if you want
interactivity, -okdir fits the bill (although maybe it would be worth adding
'-okdir command {} +'?).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?18576>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #18576] -execdir vs. PATH, Eric Blake, 2006/12/22
- [bug #18576] -execdir vs. PATH, James Youngman, 2006/12/22
- [bug #18576] -execdir vs. PATH, Eric Blake, 2006/12/22
- [bug #18576] -execdir vs. PATH, James Youngman, 2006/12/22
- [bug #18576] -execdir vs. PATH, Egmont Koblinger, 2006/12/26
- [bug #18576] -execdir vs. PATH,
Eric Blake <=
- [bug #18576] -execdir vs. PATH, James Youngman, 2006/12/29
- [bug #18576] -execdir vs. PATH, James Youngman, 2006/12/29
- [bug #18576] -execdir vs. PATH, Eric Blake, 2006/12/29