How is the wildcard * interpreted as a command?2019 Community Moderator ElectionWorking of the [0-9]Execute command within variableInternal expansion with the find command and wildcard characterCan a bash script tell what directory the user is when they run the script?Selecting non-existent files with wildcard/regexFind wildcard search not working in /etcPurpose of '&& bash' in a command (not the '&&' part, the 'bash' part)Why does a 'sudo -i' login shell break a here-doc command string argument?Bash script copy file to user's (wildcard) home dirBash wget with variables and wildcard

What Happens when Passenger Refuses to Fly Boeing 737 Max?

Reverse string, can I make it faster?

If I receive an SOS signal, what is the proper response?

At what distance can a bugbear, holding a reach weapon, with the Polearm Master feat, get their Opportunity Attack?

Why would one plane in this picture not have gear down yet?

Declaring and defining template, and specialising them

In the late 1940’s to early 1950’s what technology was available that could melt a LOT of ice?

Latex does not go to next line

Conservation of Mass and Energy

weren't playing vs didn't play

Is it possible to avoid unpacking when merging Association?

How do I express some one as a black person?

Good for you! in Russian

Shifting between bemols (flats) and diesis (sharps)in the key signature

Why the color red for the Republican Party

Should I tell my boss the work he did was worthless

Difference on montgomery curve equation between EFD and RFC7748

Bash script should only kill those instances of another script's that it has launched

Is it necessary to separate DC power cables and data cables?

How to draw cubes in a 3 dimensional plane

Why does liquid water form when we exhale on a mirror?

Is it "Vierergruppe" or "Viergruppe", or is there a distinction?

How can The Temple of Elementary Evil reliably protect itself against kinetic bombardment?

PTIJ: wiping amalek’s memory?



How is the wildcard * interpreted as a command?



2019 Community Moderator ElectionWorking of the [0-9]Execute command within variableInternal expansion with the find command and wildcard characterCan a bash script tell what directory the user is when they run the script?Selecting non-existent files with wildcard/regexFind wildcard search not working in /etcPurpose of '&& bash' in a command (not the '&&' part, the 'bash' part)Why does a 'sudo -i' login shell break a here-doc command string argument?Bash script copy file to user's (wildcard) home dirBash wget with variables and wildcard










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 *?










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 *?










    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 *?










      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






      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 4 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


















          7














          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




















          • 1





            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
            5 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
            5 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






          • 2





            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









          7














          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




















          • 1





            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
            5 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
            5 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






          • 2





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

            – Monty Harder
            2 hours ago















          7














          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




















          • 1





            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
            5 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
            5 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






          • 2





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

            – Monty Harder
            2 hours ago













          7












          7








          7







          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 2 hours ago









          DarkHeart

          3,52632340




          3,52632340










          answered 5 hours ago









          ilkkachuilkkachu

          60.9k1098174




          60.9k1098174







          • 1





            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
            5 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
            5 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






          • 2





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

            – Monty Harder
            2 hours ago












          • 1





            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
            5 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
            5 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






          • 2





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

            – Monty Harder
            2 hours ago







          1




          1





          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
          5 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
          5 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
          5 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
          5 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




          2




          2





          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

          Möglingen Índice Localización Historia Demografía Referencias Enlaces externos Menú de navegación48°53′18″N 9°07′45″E / 48.888333333333, 9.129166666666748°53′18″N 9°07′45″E / 48.888333333333, 9.1291666666667Sitio web oficial Mapa de Möglingen«Gemeinden in Deutschland nach Fläche, Bevölkerung und Postleitzahl am 30.09.2016»Möglingen

          Virtualbox - Configuration error: Querying “UUID” failed (VERR_CFGM_VALUE_NOT_FOUND)“VERR_SUPLIB_WORLD_WRITABLE” error when trying to installing OS in virtualboxVirtual Box Kernel errorFailed to open a seesion for the virtual machineFailed to open a session for the virtual machineUbuntu 14.04 LTS Virtualbox errorcan't use VM VirtualBoxusing virtualboxI can't run Linux-64 Bit on VirtualBoxUnable to insert the virtual optical disk (VBoxguestaddition) in virtual machine for ubuntu server in win 10VirtuaBox in Ubuntu 18.04 Issues with Win10.ISO Installation

          Torre de la Isleta Índice Véase también Referencias Bibliografía Enlaces externos Menú de navegación38°25′58″N 0°23′02″O / 38.43277778, -0.3838888938°25′58″N 0°23′02″O / 38.43277778, -0.38388889Torre de la Illeta de l’Horta o Torre Saleta. Base de datos de bienes inmuebles. Patrimonio Cultural. Secretaría de Estado de CulturaFicha BIC Torre de la Illeta de l’Horta. Dirección General de Patrimonio Cultural. Generalitat ValencianaLugares de interés. Ayuntamiento del CampelloTorre de la Isleta en CastillosNet.org