[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #54856] A Bit Unclear -execdir Documentation
From: |
Ahmad ElKomey |
Subject: |
[bug #54856] A Bit Unclear -execdir Documentation |
Date: |
Wed, 17 Oct 2018 12:29:05 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 |
URL:
<https://savannah.gnu.org/bugs/?54856>
Summary: A Bit Unclear -execdir Documentation
Project: findutils
Submitted by: ahmad_elkomey
Submitted on: Wed 17 Oct 2018 04:29:04 PM UTC
Category: documentation
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 4.5.11
Fixed Release: None
_______________________________________________________
Details:
I am reading the part that says:
— Action: -execdir command ;
Execute command; true if zero status is returned. find takes all arguments
after ‘-execdir’ to be part of the command until an argument consisting of
‘;’ is reached... *The command is executed in the directory in which find
was run.*
I cut some of the text after _is reached_, and bolded the part I think needs
enhancement.
I believe the part that say _The command is executed in the directory in which
find was run_ should be updated to something like:
The command is executed in the parent directory of every file matched the
criteria. Meaning, the command is executed as if you have changed the current
working directory to the one containing a matching file found by _find_
command. Also, this means that *{}* is always basename.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?54856>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [bug #54856] A Bit Unclear -execdir Documentation,
Ahmad ElKomey <=