bugfindutils - Bugs: bug #54856, A Bit Unclear -execdir...


bug #54856: A Bit Unclear -execdir Documentation

Submitted by:  Ahmad ElKomey <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:  Open/Closed:  Open
Release:  4.5.11 Fixed Release:  None

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


( Jump to the original submission)

Wed 09 Jan 2019 10:19:02 AM UTC, comment #6:

Hello Bernhard,

Thank you for your great effort maintaining and responding to others reports.

I wanted to follow up on this report. I can see that you have updated the online documentation, for another issue I reported here.

However, this issue hasn't been fixed yet.

Any updates?

Best regards,

Ahmad ElKomey <ahmad_elkomey>
Fri 19 Oct 2018 09:55:19 PM UTC, comment #5:

You already did. :-)

We're working on getting the next release out soon, so the web
pages will be updated then.

Thanks & have a nice day,

Bernhard Voelker <berny>
Project Administrator
Fri 19 Oct 2018 09:24:33 AM UTC, comment #4:

So, where should I report to get the HTML version updated?

Ahmad ElKomey <ahmad_elkomey>
Thu 18 Oct 2018 09:30:32 AM UTC, comment #3:

The HTML version is generated from the Texinfo documentation.
That in turn was improved in commit

"The command is executed in the directory which find was searching at
the time the action was executed (that is, {} will expand to a file
in the local directory)."

Unfortunately, the new HTML pages seem not to have been uploaded after the
last release. ;-(

Bernhard Voelker <berny>
Project Administrator
Wed 17 Oct 2018 06:39:26 PM UTC, comment #2:

This is the documentation I am referring to.

Where are you quoting from? (where do I get that version?)

Ahmad ElKomey <ahmad_elkomey>
Wed 17 Oct 2018 06:29:41 PM UTC, comment #1:

Where are you reading that and in which version of find?

find.1 in GIT has a very verbose wording already.
Like -exec, but the specified command is run from the subdirectory containing the matched file, which is not normally the directory in which you started find. [...]

Andreas Metzler <ametzler>
Wed 17 Oct 2018 04:29:04 PM UTC, original submission:

I am reading the part that says:

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.

Ahmad ElKomey <ahmad_elkomey>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by berny (Posted a comment)
  • -email is unavailable- added by ahmad_elkomey (Submitted the item)
  • -email is unavailable- added by ahmad_elkomey (Enhancing the wording of a confusing part in the documentation regarding execdir.)
  • -email is unavailable- added by ahmad_elkomey (Enhancing the wording of a confusing part in the documentation regarding execdir.)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-10-17 ahmad_elkomey Carbon-Copy- => Added -email is unavailable-
        Carbon-Copy- => Added -email is unavailable-

    Back to the top

    Powered by Savane 3.4