Bash Tutorial: How to Use the Command Line in Linux, Windows, and Mac Terminal

[steeBerk]

Being a beginner who wants to learn the command line this video was really helpful!! Until now I didn't even know where to start looking. Thanks!

[kyo]

I really enjoy this quick tutorial about the basics on bash still working my way to fully understand the terminal. Thank you!!!

[simwin]

Cool guide. The grey box with the list of commands appearing as you talked about them was a good touch. Made understanding what you did and remembering them easier :)

[johnscott]

You are a good person! You genuinely want to help others learn! Thank you for being a good person.

[dennismcmahon]

THANK YOU BRIANA! This is the best command line tutorial - you made it really easy to understand!

[gearboxworks]

Nice tutorial. BTW, I love how well you type!

[alexanderlewis]

Thank you that was very easy to follow and helped me understand what's going on with Bash.

[calvinebun-amu]

I feel a lot more comfortable with bash after this. Awesome!

[liliiavia]

Hi, Briana! Thank you for your new tutorial:)
Great work! :)

[kimonushki]

If anybody wants to dive a bit deeper, Michael Hartl's "Learn Enough Command Line to be Dangerous" I found to be easy to follow as a beginner, and very helpful.

[zcarfanatic]

Freecodecamp/ Briana, thank you for creating this. I am getting back into linux after many years and this is really helpful as a refresher. Your speed of delivery is perfect and I'm sure you've been refining your style over the last 3 years. One comment for others who review this material.... When you ran your good-morning script, the error you saw was "command not found". You stated the reason as a file permissions issue, but that's not accurate. If you had told the script from where to run the executable from: ./good-morning", you would have seen a "permission denied" error. The the file permissions issue would be the cause of a "permission denied" error, not a "command not found error". The "command not found" error was resolved by prepending the ./ . I get why that fixed it, but without the dot-slash, is there a default directory or path that linux is looking to run the command from? Where is default search path defined and is it editable?

[homointernetus]

Thank you very much, that's really helpful and clear

[matty]

Thanks for the information. Was directed to specifically learn BASH

[king]

This is quite helpful. Now I am no more a beginner. Thanks :)

[supriyamishra]

thank you so much Briana for sharing this

[wearethecolorofsunrise]

I really enjoyed this tutorial. A second part with more advanced scripting would be great.

[lamarati]

Can someone provide me the links that she mentions? I do not see them on the description...

[neuro]

where are all the links mentioned in the video?

[veeras]

I am using win-bash terminal and I am not able to use vi as explained in 8:40, I am receiving an error : unrecognized term type . If anyone could help

[webartem]

The video was perfect until black screen revealed at 18:20. But still very useful for newbies.

Does anyone know tutorial for git that as easy to learn as this?