Mac Equivalent to Windows CMD f8





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







3















In Windows if I entered several commands and built up a little history, I could execute previous commands by typing a prefix at the command line and pressing F8 (Windows Keyboard shortcuts) to cycle through all commands in my history matching that prefix. Is there any equivalent in MacOS?





By way of example If I sequentially executed these commands



dir .
echo IgnoreThis
dir /b %TEMP%
dir /s .
dir /b %USERPROFILE%
echo IgnoreThis


If I then entered



dir /bF8



I would first receive an autocompletion to



dir /b %TEMP%


and if I pressed F8 again it would autocomplete to



dir /b %USERPROFILE%


For another example if I instead entered



dirF8



For the first, second, and third times I pressed F8 I would get



dir .
dir /b %TEMP%
dir /s .









share|improve this question





























    3















    In Windows if I entered several commands and built up a little history, I could execute previous commands by typing a prefix at the command line and pressing F8 (Windows Keyboard shortcuts) to cycle through all commands in my history matching that prefix. Is there any equivalent in MacOS?





    By way of example If I sequentially executed these commands



    dir .
    echo IgnoreThis
    dir /b %TEMP%
    dir /s .
    dir /b %USERPROFILE%
    echo IgnoreThis


    If I then entered



    dir /bF8



    I would first receive an autocompletion to



    dir /b %TEMP%


    and if I pressed F8 again it would autocomplete to



    dir /b %USERPROFILE%


    For another example if I instead entered



    dirF8



    For the first, second, and third times I pressed F8 I would get



    dir .
    dir /b %TEMP%
    dir /s .









    share|improve this question

























      3












      3








      3








      In Windows if I entered several commands and built up a little history, I could execute previous commands by typing a prefix at the command line and pressing F8 (Windows Keyboard shortcuts) to cycle through all commands in my history matching that prefix. Is there any equivalent in MacOS?





      By way of example If I sequentially executed these commands



      dir .
      echo IgnoreThis
      dir /b %TEMP%
      dir /s .
      dir /b %USERPROFILE%
      echo IgnoreThis


      If I then entered



      dir /bF8



      I would first receive an autocompletion to



      dir /b %TEMP%


      and if I pressed F8 again it would autocomplete to



      dir /b %USERPROFILE%


      For another example if I instead entered



      dirF8



      For the first, second, and third times I pressed F8 I would get



      dir .
      dir /b %TEMP%
      dir /s .









      share|improve this question














      In Windows if I entered several commands and built up a little history, I could execute previous commands by typing a prefix at the command line and pressing F8 (Windows Keyboard shortcuts) to cycle through all commands in my history matching that prefix. Is there any equivalent in MacOS?





      By way of example If I sequentially executed these commands



      dir .
      echo IgnoreThis
      dir /b %TEMP%
      dir /s .
      dir /b %USERPROFILE%
      echo IgnoreThis


      If I then entered



      dir /bF8



      I would first receive an autocompletion to



      dir /b %TEMP%


      and if I pressed F8 again it would autocomplete to



      dir /b %USERPROFILE%


      For another example if I instead entered



      dirF8



      For the first, second, and third times I pressed F8 I would get



      dir .
      dir /b %TEMP%
      dir /s .






      terminal keyboard command-line






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 7 at 21:24









      jxramosjxramos

      1606




      1606






















          2 Answers
          2






          active

          oldest

          votes


















          2














          Add this to your ~/.inputrc:



          # ↑
          "e[A":history-search-backward
          # ↓
          "e[B":history-search-forward

          # Try to stay at the same the cursor position when moving through the history.
          set history-preserve-point on


          The way this operation works is you first type your partial command prefix and begin pressing and arrows to begin cycling in reverse and forward respectively through the command history matches to your typed prefix.






          share|improve this answer


























          • Also some useful options: gist.github.com/so-lit/c6b3661f67929fd0851ce4627e579c55

            – Yarik
            Jan 7 at 21:45






          • 1





            Spot on, just what I needed! I'm back in business, thanks a bunch.

            – jxramos
            Jan 8 at 1:38



















          1














          You may find that the Mac shell (called BASH, one of many Unix shells) is quite a bit more powerful than the Windows DOS/Powershell prompt.



          Briefly yes but autocomplete works very differently on the Mac and follows Unix shell conventions in place long before Windows/DOS was a gleam in Bill Gates eye.



          The up and down arrows will scroll backwards and forwards through the commands you have already entered. And even if you quit out of terminal all that history is remembered across sessions. Well not back to the beginning of time but BASH remembers a substantial history of commands.



          You can string multiple commands together with "&&" :



          cd /users/steve/desktop && rem picture.jpg


          That will CD to my user profile and then delete a file called picture.jpg



          Books (literally) have been written on the BASH shell and a little searching around the internet will come up with quite a lot of information on navigating, using, programming/scripting. if you don't specify the BASH shell on macOS you'll get a lot of Linux results which are generally applicable but many of the commands are different.



          If you are really interested in geeking out you can change to a different shell, there are several built-in, or another terminal program that has more features than the one that comes with macOS. Finding and using said options will be left up to you in the spirit of exploration.






          share|improve this answer































            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            Add this to your ~/.inputrc:



            # ↑
            "e[A":history-search-backward
            # ↓
            "e[B":history-search-forward

            # Try to stay at the same the cursor position when moving through the history.
            set history-preserve-point on


            The way this operation works is you first type your partial command prefix and begin pressing and arrows to begin cycling in reverse and forward respectively through the command history matches to your typed prefix.






            share|improve this answer


























            • Also some useful options: gist.github.com/so-lit/c6b3661f67929fd0851ce4627e579c55

              – Yarik
              Jan 7 at 21:45






            • 1





              Spot on, just what I needed! I'm back in business, thanks a bunch.

              – jxramos
              Jan 8 at 1:38
















            2














            Add this to your ~/.inputrc:



            # ↑
            "e[A":history-search-backward
            # ↓
            "e[B":history-search-forward

            # Try to stay at the same the cursor position when moving through the history.
            set history-preserve-point on


            The way this operation works is you first type your partial command prefix and begin pressing and arrows to begin cycling in reverse and forward respectively through the command history matches to your typed prefix.






            share|improve this answer


























            • Also some useful options: gist.github.com/so-lit/c6b3661f67929fd0851ce4627e579c55

              – Yarik
              Jan 7 at 21:45






            • 1





              Spot on, just what I needed! I'm back in business, thanks a bunch.

              – jxramos
              Jan 8 at 1:38














            2












            2








            2







            Add this to your ~/.inputrc:



            # ↑
            "e[A":history-search-backward
            # ↓
            "e[B":history-search-forward

            # Try to stay at the same the cursor position when moving through the history.
            set history-preserve-point on


            The way this operation works is you first type your partial command prefix and begin pressing and arrows to begin cycling in reverse and forward respectively through the command history matches to your typed prefix.






            share|improve this answer















            Add this to your ~/.inputrc:



            # ↑
            "e[A":history-search-backward
            # ↓
            "e[B":history-search-forward

            # Try to stay at the same the cursor position when moving through the history.
            set history-preserve-point on


            The way this operation works is you first type your partial command prefix and begin pressing and arrows to begin cycling in reverse and forward respectively through the command history matches to your typed prefix.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Jan 9 at 21:32









            jxramos

            1606




            1606










            answered Jan 7 at 21:42









            YarikYarik

            813




            813













            • Also some useful options: gist.github.com/so-lit/c6b3661f67929fd0851ce4627e579c55

              – Yarik
              Jan 7 at 21:45






            • 1





              Spot on, just what I needed! I'm back in business, thanks a bunch.

              – jxramos
              Jan 8 at 1:38



















            • Also some useful options: gist.github.com/so-lit/c6b3661f67929fd0851ce4627e579c55

              – Yarik
              Jan 7 at 21:45






            • 1





              Spot on, just what I needed! I'm back in business, thanks a bunch.

              – jxramos
              Jan 8 at 1:38

















            Also some useful options: gist.github.com/so-lit/c6b3661f67929fd0851ce4627e579c55

            – Yarik
            Jan 7 at 21:45





            Also some useful options: gist.github.com/so-lit/c6b3661f67929fd0851ce4627e579c55

            – Yarik
            Jan 7 at 21:45




            1




            1





            Spot on, just what I needed! I'm back in business, thanks a bunch.

            – jxramos
            Jan 8 at 1:38





            Spot on, just what I needed! I'm back in business, thanks a bunch.

            – jxramos
            Jan 8 at 1:38













            1














            You may find that the Mac shell (called BASH, one of many Unix shells) is quite a bit more powerful than the Windows DOS/Powershell prompt.



            Briefly yes but autocomplete works very differently on the Mac and follows Unix shell conventions in place long before Windows/DOS was a gleam in Bill Gates eye.



            The up and down arrows will scroll backwards and forwards through the commands you have already entered. And even if you quit out of terminal all that history is remembered across sessions. Well not back to the beginning of time but BASH remembers a substantial history of commands.



            You can string multiple commands together with "&&" :



            cd /users/steve/desktop && rem picture.jpg


            That will CD to my user profile and then delete a file called picture.jpg



            Books (literally) have been written on the BASH shell and a little searching around the internet will come up with quite a lot of information on navigating, using, programming/scripting. if you don't specify the BASH shell on macOS you'll get a lot of Linux results which are generally applicable but many of the commands are different.



            If you are really interested in geeking out you can change to a different shell, there are several built-in, or another terminal program that has more features than the one that comes with macOS. Finding and using said options will be left up to you in the spirit of exploration.






            share|improve this answer




























              1














              You may find that the Mac shell (called BASH, one of many Unix shells) is quite a bit more powerful than the Windows DOS/Powershell prompt.



              Briefly yes but autocomplete works very differently on the Mac and follows Unix shell conventions in place long before Windows/DOS was a gleam in Bill Gates eye.



              The up and down arrows will scroll backwards and forwards through the commands you have already entered. And even if you quit out of terminal all that history is remembered across sessions. Well not back to the beginning of time but BASH remembers a substantial history of commands.



              You can string multiple commands together with "&&" :



              cd /users/steve/desktop && rem picture.jpg


              That will CD to my user profile and then delete a file called picture.jpg



              Books (literally) have been written on the BASH shell and a little searching around the internet will come up with quite a lot of information on navigating, using, programming/scripting. if you don't specify the BASH shell on macOS you'll get a lot of Linux results which are generally applicable but many of the commands are different.



              If you are really interested in geeking out you can change to a different shell, there are several built-in, or another terminal program that has more features than the one that comes with macOS. Finding and using said options will be left up to you in the spirit of exploration.






              share|improve this answer


























                1












                1








                1







                You may find that the Mac shell (called BASH, one of many Unix shells) is quite a bit more powerful than the Windows DOS/Powershell prompt.



                Briefly yes but autocomplete works very differently on the Mac and follows Unix shell conventions in place long before Windows/DOS was a gleam in Bill Gates eye.



                The up and down arrows will scroll backwards and forwards through the commands you have already entered. And even if you quit out of terminal all that history is remembered across sessions. Well not back to the beginning of time but BASH remembers a substantial history of commands.



                You can string multiple commands together with "&&" :



                cd /users/steve/desktop && rem picture.jpg


                That will CD to my user profile and then delete a file called picture.jpg



                Books (literally) have been written on the BASH shell and a little searching around the internet will come up with quite a lot of information on navigating, using, programming/scripting. if you don't specify the BASH shell on macOS you'll get a lot of Linux results which are generally applicable but many of the commands are different.



                If you are really interested in geeking out you can change to a different shell, there are several built-in, or another terminal program that has more features than the one that comes with macOS. Finding and using said options will be left up to you in the spirit of exploration.






                share|improve this answer













                You may find that the Mac shell (called BASH, one of many Unix shells) is quite a bit more powerful than the Windows DOS/Powershell prompt.



                Briefly yes but autocomplete works very differently on the Mac and follows Unix shell conventions in place long before Windows/DOS was a gleam in Bill Gates eye.



                The up and down arrows will scroll backwards and forwards through the commands you have already entered. And even if you quit out of terminal all that history is remembered across sessions. Well not back to the beginning of time but BASH remembers a substantial history of commands.



                You can string multiple commands together with "&&" :



                cd /users/steve/desktop && rem picture.jpg


                That will CD to my user profile and then delete a file called picture.jpg



                Books (literally) have been written on the BASH shell and a little searching around the internet will come up with quite a lot of information on navigating, using, programming/scripting. if you don't specify the BASH shell on macOS you'll get a lot of Linux results which are generally applicable but many of the commands are different.



                If you are really interested in geeking out you can change to a different shell, there are several built-in, or another terminal program that has more features than the one that comes with macOS. Finding and using said options will be left up to you in the spirit of exploration.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 7 at 21:44









                Steve ChambersSteve Chambers

                15.1k21740




                15.1k21740















                    Popular posts from this blog

                    To store a contact into the json file from server.js file using a class in NodeJS

                    Redirect URL with Chrome Remote Debugging Android Devices

                    Dieringhausen