How to change profile to search current directory?











up vote
0
down vote

favorite












I would like to change my profile so that I can execute programs in the current directory without ./.



In other words:



$ foo.sh


would accomplish what currently happens with:



$ ./foo.sh









share|improve this question




























    up vote
    0
    down vote

    favorite












    I would like to change my profile so that I can execute programs in the current directory without ./.



    In other words:



    $ foo.sh


    would accomplish what currently happens with:



    $ ./foo.sh









    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I would like to change my profile so that I can execute programs in the current directory without ./.



      In other words:



      $ foo.sh


      would accomplish what currently happens with:



      $ ./foo.sh









      share|improve this question















      I would like to change my profile so that I can execute programs in the current directory without ./.



      In other words:



      $ foo.sh


      would accomplish what currently happens with:



      $ ./foo.sh






      command-line profile






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 24 at 20:31









      Rui F Ribeiro

      38.3k1475126




      38.3k1475126










      asked Jun 11 '11 at 10:13









      Eric Wilson

      1,89172439




      1,89172439






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          4
          down vote



          accepted










          This is generally considered a very dangerous idea because it introduces the possibility that you will be tricked into executing something thinking it is something else. Say for example that somebody puts an executable named "cd" in /tmp. Being able to run things in the current folder without specifying an explicit path might mean you inadvertently run that script (that could be malicious) as your user while expecting to just cd somewhere else on the system.



          That being said you can affect this by adding ./ to your program execution path.



          export PATH=$PATH:./


          If you put that line in your ~/.profile it should be available in any new shells you open.






          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',
            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%2f14812%2fhow-to-change-profile-to-search-current-directory%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








            up vote
            4
            down vote



            accepted










            This is generally considered a very dangerous idea because it introduces the possibility that you will be tricked into executing something thinking it is something else. Say for example that somebody puts an executable named "cd" in /tmp. Being able to run things in the current folder without specifying an explicit path might mean you inadvertently run that script (that could be malicious) as your user while expecting to just cd somewhere else on the system.



            That being said you can affect this by adding ./ to your program execution path.



            export PATH=$PATH:./


            If you put that line in your ~/.profile it should be available in any new shells you open.






            share|improve this answer

























              up vote
              4
              down vote



              accepted










              This is generally considered a very dangerous idea because it introduces the possibility that you will be tricked into executing something thinking it is something else. Say for example that somebody puts an executable named "cd" in /tmp. Being able to run things in the current folder without specifying an explicit path might mean you inadvertently run that script (that could be malicious) as your user while expecting to just cd somewhere else on the system.



              That being said you can affect this by adding ./ to your program execution path.



              export PATH=$PATH:./


              If you put that line in your ~/.profile it should be available in any new shells you open.






              share|improve this answer























                up vote
                4
                down vote



                accepted







                up vote
                4
                down vote



                accepted






                This is generally considered a very dangerous idea because it introduces the possibility that you will be tricked into executing something thinking it is something else. Say for example that somebody puts an executable named "cd" in /tmp. Being able to run things in the current folder without specifying an explicit path might mean you inadvertently run that script (that could be malicious) as your user while expecting to just cd somewhere else on the system.



                That being said you can affect this by adding ./ to your program execution path.



                export PATH=$PATH:./


                If you put that line in your ~/.profile it should be available in any new shells you open.






                share|improve this answer












                This is generally considered a very dangerous idea because it introduces the possibility that you will be tricked into executing something thinking it is something else. Say for example that somebody puts an executable named "cd" in /tmp. Being able to run things in the current folder without specifying an explicit path might mean you inadvertently run that script (that could be malicious) as your user while expecting to just cd somewhere else on the system.



                That being said you can affect this by adding ./ to your program execution path.



                export PATH=$PATH:./


                If you put that line in your ~/.profile it should be available in any new shells you open.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jun 11 '11 at 10:33









                Caleb

                50k9146190




                50k9146190






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f14812%2fhow-to-change-profile-to-search-current-directory%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

                    Accessing regular linux commands in Huawei's Dopra Linux

                    Can't connect RFCOMM socket: Host is down

                    Kernel panic - not syncing: Fatal Exception in Interrupt