How is the wildcard * interpreted as a command?












2















I know how * is interpreted in commands like ls for example. But when trying to run * as a command the shell tries to execute the first file or directory in your working directory. Why is this? How does the shell understand *?






bash wildcards







share|improve this question









New contributor




osmak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    2















    I know how * is interpreted in commands like ls for example. But when trying to run * as a command the shell tries to execute the first file or directory in your working directory. Why is this? How does the shell understand *?






    bash wildcards







    share|improve this question









    New contributor




    osmak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      2












      2








      2








      I know how * is interpreted in commands like ls for example. But when trying to run * as a command the shell tries to execute the first file or directory in your working directory. Why is this? How does the shell understand *?






      bash wildcards







      share|improve this question









      New contributor




      osmak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I know how * is interpreted in commands like ls for example. But when trying to run * as a command the shell tries to execute the first file or directory in your working directory. Why is this? How does the shell understand *?






      bash wildcards




      bash wildcards






      share|improve this question









      New contributor




      osmak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      osmak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 3 hours ago









      Glorfindel

      2991411




      2991411






      New contributor




      osmak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 5 hours ago









      osmakosmak

      133




      133




      New contributor




      osmak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      osmak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      osmak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          1 Answer
          1






          active

          oldest

          votes


















          6














          Unlike in some other operating systems, in Unixes, it's the shell that expands filename wildcards. It expands parameter expansions and globs first, then uses the (now) first word as the name for the command to run.



          This is also why files named with a leading dash can be troublesome: a glob like * will expand to the file names, and a name starting with a dash may be taken as an option. (The scary example being that a file called -r in the working directory would make rm * remove everything recursively...)



          Usually, one wouldn't use * as the first item on any command line, though, so having the first file determine the command to run in that case isn't likely to cause problems.






          share|improve this answer


























          • I think this example misses an important point out, that filename expansion is not subject to further field splitting, unlike parameter expansion, so filenames with spaces are still safe.

            – Michael Homer
            4 hours ago











          • OK, so I think I misunderstood how the * work in the first place. I thought that it is a common syntax used in Linux commands. But, if I understood your answer correctly, then filename expansion is a shell feature not a command feature. So what happened is that * got replaced by all file or directory names in PWD but when the shell tried executing the first one it produced the error I saw.

            – osmak
            4 hours ago











          • @osmak, yeah, it's a shell feature on Unixes. Easier that way, so each and every program doesn't have to implement it. Though of course programs like find know how to expand similar patterns, too (e.g. file -name "*.txt")

            – ilkkachu
            4 hours ago











          • @osmak That is a correct understanding.

            – Kusalananda
            4 hours ago






          • 1





            A file named -r is bad, but one named -rf is even worse.

            – Monty Harder
            2 hours ago











          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
          });


          }
          });






          osmak is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505707%2fhow-is-the-wildcard-interpreted-as-a-command%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









          6














          Unlike in some other operating systems, in Unixes, it's the shell that expands filename wildcards. It expands parameter expansions and globs first, then uses the (now) first word as the name for the command to run.



          This is also why files named with a leading dash can be troublesome: a glob like * will expand to the file names, and a name starting with a dash may be taken as an option. (The scary example being that a file called -r in the working directory would make rm * remove everything recursively...)



          Usually, one wouldn't use * as the first item on any command line, though, so having the first file determine the command to run in that case isn't likely to cause problems.






          share|improve this answer


























          • I think this example misses an important point out, that filename expansion is not subject to further field splitting, unlike parameter expansion, so filenames with spaces are still safe.

            – Michael Homer
            4 hours ago











          • OK, so I think I misunderstood how the * work in the first place. I thought that it is a common syntax used in Linux commands. But, if I understood your answer correctly, then filename expansion is a shell feature not a command feature. So what happened is that * got replaced by all file or directory names in PWD but when the shell tried executing the first one it produced the error I saw.

            – osmak
            4 hours ago











          • @osmak, yeah, it's a shell feature on Unixes. Easier that way, so each and every program doesn't have to implement it. Though of course programs like find know how to expand similar patterns, too (e.g. file -name "*.txt")

            – ilkkachu
            4 hours ago











          • @osmak That is a correct understanding.

            – Kusalananda
            4 hours ago






          • 1





            A file named -r is bad, but one named -rf is even worse.

            – Monty Harder
            2 hours ago
















          6














          Unlike in some other operating systems, in Unixes, it's the shell that expands filename wildcards. It expands parameter expansions and globs first, then uses the (now) first word as the name for the command to run.



          This is also why files named with a leading dash can be troublesome: a glob like * will expand to the file names, and a name starting with a dash may be taken as an option. (The scary example being that a file called -r in the working directory would make rm * remove everything recursively...)



          Usually, one wouldn't use * as the first item on any command line, though, so having the first file determine the command to run in that case isn't likely to cause problems.






          share|improve this answer


























          • I think this example misses an important point out, that filename expansion is not subject to further field splitting, unlike parameter expansion, so filenames with spaces are still safe.

            – Michael Homer
            4 hours ago











          • OK, so I think I misunderstood how the * work in the first place. I thought that it is a common syntax used in Linux commands. But, if I understood your answer correctly, then filename expansion is a shell feature not a command feature. So what happened is that * got replaced by all file or directory names in PWD but when the shell tried executing the first one it produced the error I saw.

            – osmak
            4 hours ago











          • @osmak, yeah, it's a shell feature on Unixes. Easier that way, so each and every program doesn't have to implement it. Though of course programs like find know how to expand similar patterns, too (e.g. file -name "*.txt")

            – ilkkachu
            4 hours ago











          • @osmak That is a correct understanding.

            – Kusalananda
            4 hours ago






          • 1





            A file named -r is bad, but one named -rf is even worse.

            – Monty Harder
            2 hours ago














          6












          6








          6







          Unlike in some other operating systems, in Unixes, it's the shell that expands filename wildcards. It expands parameter expansions and globs first, then uses the (now) first word as the name for the command to run.



          This is also why files named with a leading dash can be troublesome: a glob like * will expand to the file names, and a name starting with a dash may be taken as an option. (The scary example being that a file called -r in the working directory would make rm * remove everything recursively...)



          Usually, one wouldn't use * as the first item on any command line, though, so having the first file determine the command to run in that case isn't likely to cause problems.






          share|improve this answer















          Unlike in some other operating systems, in Unixes, it's the shell that expands filename wildcards. It expands parameter expansions and globs first, then uses the (now) first word as the name for the command to run.



          This is also why files named with a leading dash can be troublesome: a glob like * will expand to the file names, and a name starting with a dash may be taken as an option. (The scary example being that a file called -r in the working directory would make rm * remove everything recursively...)



          Usually, one wouldn't use * as the first item on any command line, though, so having the first file determine the command to run in that case isn't likely to cause problems.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 1 hour ago









          DarkHeart

          3,52632340




          3,52632340










          answered 5 hours ago









          ilkkachuilkkachu

          60.9k1098174




          60.9k1098174













          • I think this example misses an important point out, that filename expansion is not subject to further field splitting, unlike parameter expansion, so filenames with spaces are still safe.

            – Michael Homer
            4 hours ago











          • OK, so I think I misunderstood how the * work in the first place. I thought that it is a common syntax used in Linux commands. But, if I understood your answer correctly, then filename expansion is a shell feature not a command feature. So what happened is that * got replaced by all file or directory names in PWD but when the shell tried executing the first one it produced the error I saw.

            – osmak
            4 hours ago











          • @osmak, yeah, it's a shell feature on Unixes. Easier that way, so each and every program doesn't have to implement it. Though of course programs like find know how to expand similar patterns, too (e.g. file -name "*.txt")

            – ilkkachu
            4 hours ago











          • @osmak That is a correct understanding.

            – Kusalananda
            4 hours ago






          • 1





            A file named -r is bad, but one named -rf is even worse.

            – Monty Harder
            2 hours ago



















          • I think this example misses an important point out, that filename expansion is not subject to further field splitting, unlike parameter expansion, so filenames with spaces are still safe.

            – Michael Homer
            4 hours ago











          • OK, so I think I misunderstood how the * work in the first place. I thought that it is a common syntax used in Linux commands. But, if I understood your answer correctly, then filename expansion is a shell feature not a command feature. So what happened is that * got replaced by all file or directory names in PWD but when the shell tried executing the first one it produced the error I saw.

            – osmak
            4 hours ago











          • @osmak, yeah, it's a shell feature on Unixes. Easier that way, so each and every program doesn't have to implement it. Though of course programs like find know how to expand similar patterns, too (e.g. file -name "*.txt")

            – ilkkachu
            4 hours ago











          • @osmak That is a correct understanding.

            – Kusalananda
            4 hours ago






          • 1





            A file named -r is bad, but one named -rf is even worse.

            – Monty Harder
            2 hours ago

















          I think this example misses an important point out, that filename expansion is not subject to further field splitting, unlike parameter expansion, so filenames with spaces are still safe.

          – Michael Homer
          4 hours ago





          I think this example misses an important point out, that filename expansion is not subject to further field splitting, unlike parameter expansion, so filenames with spaces are still safe.

          – Michael Homer
          4 hours ago













          OK, so I think I misunderstood how the * work in the first place. I thought that it is a common syntax used in Linux commands. But, if I understood your answer correctly, then filename expansion is a shell feature not a command feature. So what happened is that * got replaced by all file or directory names in PWD but when the shell tried executing the first one it produced the error I saw.

          – osmak
          4 hours ago





          OK, so I think I misunderstood how the * work in the first place. I thought that it is a common syntax used in Linux commands. But, if I understood your answer correctly, then filename expansion is a shell feature not a command feature. So what happened is that * got replaced by all file or directory names in PWD but when the shell tried executing the first one it produced the error I saw.

          – osmak
          4 hours ago













          @osmak, yeah, it's a shell feature on Unixes. Easier that way, so each and every program doesn't have to implement it. Though of course programs like find know how to expand similar patterns, too (e.g. file -name "*.txt")

          – ilkkachu
          4 hours ago





          @osmak, yeah, it's a shell feature on Unixes. Easier that way, so each and every program doesn't have to implement it. Though of course programs like find know how to expand similar patterns, too (e.g. file -name "*.txt")

          – ilkkachu
          4 hours ago













          @osmak That is a correct understanding.

          – Kusalananda
          4 hours ago





          @osmak That is a correct understanding.

          – Kusalananda
          4 hours ago




          1




          1





          A file named -r is bad, but one named -rf is even worse.

          – Monty Harder
          2 hours ago





          A file named -r is bad, but one named -rf is even worse.

          – Monty Harder
          2 hours ago










          osmak is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          osmak is a new contributor. Be nice, and check out our Code of Conduct.













          osmak is a new contributor. Be nice, and check out our Code of Conduct.












          osmak is a new contributor. Be nice, and check out our Code of Conduct.
















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505707%2fhow-is-the-wildcard-interpreted-as-a-command%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

          Ponta tanko

          Image
          Usona ponta tanko M60A1 Ponta tanko estas, simile kiel kirasita savveturilo, inter specialaj kirasitaj transportiloj. Kiel pontaj tankoj eblas konsideri ĉiujn memmovigaj rimedoj ebligantaj superi obstaklojn ĝis larĝeco 24 metroj rekte en spaco de bataloperacoj. Ties ĉefa tasko estas ebligi al la propraj taĉmentoj daŭrigi en rapida antaŭenirado sen senbezona reteniĝo. El tio pli-malpli rezultas taktikaj-teknikaj postuloj, kiujn ili devas plenumi. Precipe temas pri kapablo operacii komune kun unue-sinsekvaj taĉmentoj kaj transpontigi obstaklojn dum kelke da minutoj. This page is only for reference, If you need detailed information, please check here
          Read more

          Tantalo (mitologio)

          Image
          Ĉi tiu artikolo temas pri mitologio. Por aliaj signifoj vidu la paĝon Tantalo (apartigilo) . Tantalo , laŭ Gioacchino Assereto. Laŭ la helena mitologio, Tantalo (el la greka Τάνταλος , ŝancelanta aŭ tre malfeliĉa ) estis filo de Zeŭso kaj la oceanidino Pluto, laŭ la plej divastigata versio. Li estis reĝo de Frigio [1] aŭ de la monto Sipilo, en Lidio (Malgrandazio) [2] kaj post sia morto li suferis eternan torturadon ĉe la Tartaro, la plej profunda parto de Hadeso, rezervita por la plej perversaj homoj. Tamen, kelkaj rakontoj asertas ke li estis reĝo de Argo aŭ de Korinto [3] , aŭ ke li migris norden el la monto Sipilo por akiri la tronon de Paflagonio, el kie Ilo forpelis lin pro tio, ke Tantalo forkaptis kaj seksperfortis lian fraton Ganimedon [4] , kaj tiel ofendis la diojn. Verŝajne li ankaŭ regis urbon en okcidenta Anatolio, kiun oni nomis Tantalis [5] pro li, aŭ Sipilo , pro la monto sur kies flanko ankoraŭ staras ĝiaj ruinaĵoj [6] . Laŭ la geografiisto Strabo,...
          Read more

          Erzsébet Schaár

          Image
          Erzsébet Schaár Memportreto de Erzsébet Schaár en Pécs Personaj informoj Naskiĝo 27-an de julio 1908 ( 1908-07-27 ) en Budafok Morto 29-an de aŭgusto 1975 ( 1975-08-29 ) (67-jara) en Budapeŝto Ŝtataneco Hungario Profesio skulptisto Familianoj Edz(in)o Tibor Vilt v   •   d   •   r Erzsébet Schaár [erĵEbet ŝAr], laŭ hungarlingve kutima sinsekvo Schaár Erzsébet estis hungara skulptisto. Ŝia edzo estis Tibor Vilt. Déryné Széppataki Róza en Miskolc fare de Erzsébet Schaár Erzsébet Schaár [1] naskiĝis la 27-an de julio 1908 en Budafok, ŝi mortis la 29-an de aŭgusto 1975 en Budapeŝto. Enhavo 1 Biografio 2 Elektitaj solaj ekspozicioj 3 Elektitaj kolektivaj ekspozicioj 4 Elektitaj skulptaĵoj 5 Elektitaj disĉiploj 6 Fontoj 7 Referencoj Biografio | Erzsébet Schaár studis en Industriarta Lernejo, poste en Reĝa Belarta Altlernejo (1924-1926). Ŝia ĉefinstruisto estis Zsig...
          Read more