Why is find piping in non directories when the “-type d” test is used?












1














I have a directory



~/root/
|-- bar
|-- eggs
|-- foo
|-- hello.txt
|-- script.sh
`-- spam

4 directories, 2 files


Issuing find . -type d while in ~/root/ yields



.
./spam
./eggs
./bar
./foo


However, issuing find . -type d | parallel "echo {}" ::: * yields



bar
eggs
foo
hello.txt
script.sh
spam


Why are the nondirectories hello.txt and script.sh piped here?










share|improve this question





























    1














    I have a directory



    ~/root/
    |-- bar
    |-- eggs
    |-- foo
    |-- hello.txt
    |-- script.sh
    `-- spam

    4 directories, 2 files


    Issuing find . -type d while in ~/root/ yields



    .
    ./spam
    ./eggs
    ./bar
    ./foo


    However, issuing find . -type d | parallel "echo {}" ::: * yields



    bar
    eggs
    foo
    hello.txt
    script.sh
    spam


    Why are the nondirectories hello.txt and script.sh piped here?










    share|improve this question



























      1












      1








      1







      I have a directory



      ~/root/
      |-- bar
      |-- eggs
      |-- foo
      |-- hello.txt
      |-- script.sh
      `-- spam

      4 directories, 2 files


      Issuing find . -type d while in ~/root/ yields



      .
      ./spam
      ./eggs
      ./bar
      ./foo


      However, issuing find . -type d | parallel "echo {}" ::: * yields



      bar
      eggs
      foo
      hello.txt
      script.sh
      spam


      Why are the nondirectories hello.txt and script.sh piped here?










      share|improve this question















      I have a directory



      ~/root/
      |-- bar
      |-- eggs
      |-- foo
      |-- hello.txt
      |-- script.sh
      `-- spam

      4 directories, 2 files


      Issuing find . -type d while in ~/root/ yields



      .
      ./spam
      ./eggs
      ./bar
      ./foo


      However, issuing find . -type d | parallel "echo {}" ::: * yields



      bar
      eggs
      foo
      hello.txt
      script.sh
      spam


      Why are the nondirectories hello.txt and script.sh piped here?







      find pipe gnu-parallel






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 29 mins ago









      Warren Young

      54.5k10142146




      54.5k10142146










      asked 8 hours ago









      Brian Fitzpatrick

      7961923




      7961923






















          1 Answer
          1






          active

          oldest

          votes


















          8














          According to the manual, the ::: * syntax uses the shell's expansion of * as an argument list instead of anything from stdin. So as written, your command ignores the result of find and passes all files in the current directory as arguments. If you leave off the ::: *, it should work as intended.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490557%2fwhy-is-find-piping-in-non-directories-when-the-type-d-test-is-used%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            8














            According to the manual, the ::: * syntax uses the shell's expansion of * as an argument list instead of anything from stdin. So as written, your command ignores the result of find and passes all files in the current directory as arguments. If you leave off the ::: *, it should work as intended.






            share|improve this answer




























              8














              According to the manual, the ::: * syntax uses the shell's expansion of * as an argument list instead of anything from stdin. So as written, your command ignores the result of find and passes all files in the current directory as arguments. If you leave off the ::: *, it should work as intended.






              share|improve this answer


























                8












                8








                8






                According to the manual, the ::: * syntax uses the shell's expansion of * as an argument list instead of anything from stdin. So as written, your command ignores the result of find and passes all files in the current directory as arguments. If you leave off the ::: *, it should work as intended.






                share|improve this answer














                According to the manual, the ::: * syntax uses the shell's expansion of * as an argument list instead of anything from stdin. So as written, your command ignores the result of find and passes all files in the current directory as arguments. If you leave off the ::: *, it should work as intended.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 5 hours ago

























                answered 7 hours ago









                Fox

                5,10611131




                5,10611131






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490557%2fwhy-is-find-piping-in-non-directories-when-the-type-d-test-is-used%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    サソリ

                    広島県道265号伴広島線

                    Setup Asymptote in Texstudio