Become a bash scripting pro - full course

In this video you'll learn everything you need to know in order to start writing bash scripts to automate all of your boring tasks.
Useful reference site: learnxinyminutes.com/docs/bash/
Music by Alex Bainter / CC BY
#terminal #linux #bash

[@thisguyc0ry]

I never knew I needed a “Guided Bash Meditation”

[@RickGladwin]

Pro tip: light a couple candles, put on a nice essential oil diffuser. Saje has a scent called “nerd forest” that’s perfect for this.

[@nomemeshere253]

If you made Bash Pro Shop merch, I would instantly buy it. I have never bought merch before, but it would be worth the investment.

[@Kane0123]

I second this. Only stopped for the title

[@SteveWilburn]

For real. That graphic would be great on a shirt or a hat.

[@hunterlake2943]

Same

[@moose-1]

Agreed

[@Iwbyiwm]

I agree

[@danydanger]

I have been through long courses of bash scripting and in that only I have seen all these topics covered, covering so much in a less than 30mins is really awesome. I request you to make more of like this plz.

[@leo25cm]

It's interesting that not a lot of creators go in-depth into she'll scripting. It's so useful and portable

[@kurdm1482]

Shell scripting is easy n powerful ​@@leo25cm

[@RickGladwin]

I consider myself to be “decent to okay” at bash scripting. I’ve even got bash scripts in enterprise production environments. This video helped _clarify_ and illuminate so many individual features and (sometimes conflicting) syntaxes. Not only do I have new knowledge, but the information that was already in my head is more cohesive. Absolute A+ content.

[@CODE_IS_EVERYTHING]

That is great to hear!

[@aarond0623]

A couple of errors/things that may be confusing: 13:53 - The internal logical AND and OR are wrong for double brackets. They would be correct for single brackets, though. 20:07 - The for loop is incorrect and prints 1[@]. The correct syntax would be `for item in "${my_arr[@]}"` 21:00 - Not an error, but this while loop will fail after the first iteration with the previously mentioned "strict mode", because ((counter++)) will return non-zero and exit the script.

[@polares8187]

You keep hitting it out of the park. Another amazing video. Holy hell.

[@ericlindell3777]

Wonderful vid! Looking forward to more!

[@pabloqp7929]

So many pro-tips and nuanced demos, thank you! Also great voice tbf.

[@frackinfamous6126]

Please don’t stop making videos. ❤. Keep it up! Too good.

[@DenisNolan]

I feel like I’m learning and meditating at the same time. This is wonderful. Subscribed

[@erikastjarnstoft]

So glad I found your channel as I'm struggling to wrap my head around the awkwardness of writing bash scrips for my studies right now. Will definitely reference parts of this video again during the two weeks I have for my current assignment! Thank you! ❤

[@finnberuldsen4798]

Awesome video, so much content, so well explained. Love the added process at the end

[@silvertechnolo3958]

This was beautiful my friend. Your calming voice and the methodical breakdown of the code is Buddhist in nature. Incredible work. And I now second the merch thing.

[@CODE_IS_EVERYTHING]

Thanks!

[@hellawacked]

Great videos looking forward to the next one.

[@M3eizo]

Really awesome! Thank you so much and see you in the next one too.

[@redbrickhut]

Dude your content is amazing, keep it up!

[@SCALENE5]

Thank you for teaching me. This is top grade knowledge that you are teaching us.

[@SocheatSok78]

In the function statement you can also use the “return” keyword “return” or “return n”.

[@ajko000]

I had some trouble understanding how the positional variables worked until I saw the ffmpeg example and then it clicked! Thanks!

[@franciscocarvalho8843]

Hey, you did an amazing job. This was more than helpful, it was enjoyable. I believe that you have an excellent combination here, summarizing information but also lifting a bit the curtain to understand the underlying structure is really valuable for this type of content. Keep up and I am sure that you will get more acknowledgment from everyone in a near future!

[@youseflourdx6531]

Thanks a lot! I'm learning bash little by little and this video and the last one hit the spot

[@CODE_IS_EVERYTHING]

I’m glad to hear it!

[@rafadubiel5288]

Great video! Need more! 👏

[@tonyb9864]

Thanks! More of this please! 🙂

[@snneossi6880]

Really interesting. and concise, kudos!!!

[@goofballbiscuits3647]

Nice mic, damn 😅 Even better video! It's actually as relaxing as it is perfectly dense and presented. I think any more in any direction of brevity or speed, it wouldn't work. You hit that Cinderella slipper of YT education. Normally, music in the background drives me nuts. I loved it!

[@CODE_IS_EVERYTHING]

Thanks!

[@blank001]

Thanks for this awesome video/resource

[@MacSuperior_]

thx for the video! I’m sure learning this will help me in the future

[@caiocouto3450]

this vid is amazing. I'm not very inclined to learn shell scripts, like bash or powershell; but the pacing, the background song, the edit and your explanation turn it like a "reading session". i felt like i was reading a really good book, with no hurry and pay the most attention i could

[@CODE_IS_EVERYTHING]

Glad you enjoyed it!

[@josephbledsoe1333]

Was skeptical I would learn anything new, but there were several juicy fresh bits! Very cohesive, wish I had seen this years ago haha. Valuable content for the community

[@CODE_IS_EVERYTHING]

Glad to hear it!

[@mingzih]

nice, you acually explained all about bash, thanks.

[@alezad57121]

more videos exactly like this. fundamentals of linux is great stuff.

[@kartikmahajan4405]

great video, subscribed

[@saeedxgholami]

Very useful thanks.

[@azadim8268]

Thank you sir!

[@trev-dev]

Telling me that bash is a command syntax language unravels much of the mystery behind why my scripts have sucked. Thanks

[@SlinkyD]

This is the ABS (Advanced Bash Scripting) Guide speed run.

[@XrayShapeShifter]

This video is an expected pleasure

[@l.sureshkumar-lsk550]

Nice useful video. 👏

[@alexander_adnan]

The title got me, there’s one that just opened near my place😂😂😂😂😂❤

[@made-simple]

Really unique Editing style ... feels calming and mental rush just boils down! ... Subscribed! for your efforts !

[@CODE_IS_EVERYTHING]

Thanks!

[@Juanjuanzerojuan]

Super helpful thank you!

[@CODE_IS_EVERYTHING]

I’m glad to hear it!

[@sevos]

This video is awesome

[@phobosmoon4643]

dank content the middle school teachers need to steal this and create some yung engineers

[@imaboutmyfathersbusiness]

Subscribed Brother!

[@kurdm1482]

I love this n you Thank you

[@Podoco_music]

fantastic video! this ends up being a good refresher video too!

[@mgmartin51]

I feel like I’m listening to late night FM radio.

[@comosaycomosah]

Lmao love the thumbnail 😂

[@leo25cm]

Also if you stick to the Bash test, that is `[[ ... ]]`, you don't need to put variables inside quotes, not on the left side of a comparison.

[@darkseid3427]

thanks a ton!! can you please make video or if possible share reference sites for learning docker and k8s.

[@CODE_IS_EVERYTHING]

Hey, I've been thinking about doing guide videos for those. I've got a couple others in the works right now, but I can definitely do that.

[@Eutropios]

Fantastic video. I'll definitely be showing this to others who may need help with bash scripting. It's also worth pointing out that a lot of these (but not all) commands and syntaxes can be applied to ksh/mksh, dash and POSIX shell, and zsh too!

[@MorphTW]

thanks for sharing. here is the comment for the algo!

[@Robdawger]

You're the best. I followed along and made a "quick reference" guide for myself as I continue to learn how to use Bash and Linux/Ubuntu. It's not as scary as I thought it would be, trying to learn all this. Thank you for making it much more approachable! One question: Is there is significant difference between csh and bash? My advisor only uses csh, while, I want to learn more bash/tcsh, since I've read that the latter is a bit more dynamic compared to csh. Is this true?

[@CODE_IS_EVERYTHING]

I'm glad to hear it! And I think the choice really comes down to personal preference. There will be some differences in syntax and a few features here and there, but the majority of the work you'll be doing in the scripting is going to be very similar, as it'll be heavily command driven. I think the real reason to opt for bash is its ubiquity. Almost every unix system will have bash pre-installed, whereas very few have csh/tcsh (not that its hard to install). I personally use zsh as my main shell, but still for any scripts I write I'll tell it to use bash so it'll run on any of my systems.

[@goofballbiscuits3647]

I'll add that Bash is used in Unix, Linux and Windows. If you are going professional with these skills, bash would be the most useful/ubiquitous by far.

[@hyltoncarboo8303]

This is golden!!! What font do you use for the terminal?

[@CODE_IS_EVERYTHING]

Thanks! And its IBM Plex Mono (www.programmingfonts.org/#plex-mono)

[@cherkim]

This production quality is too high, the channel will blow up soon.

[@mervmartin2112]

Bash is cow complete! cowsay "Thanks! You have another subscriber."

[@Gabriel_Bento]

This man is a legend. I always thought bash was a hard and weird language. Now I realize it's not that hard, but still weird as mentioned. Thanks! :D

[@CODE_IS_EVERYTHING]

I’m glad to hear it!

[@doskius111]

I do not know if someone address this but during 13:54 there is an syntax error in internals, instead of [[]] you have to use [], because -a/-o are for POSIX standard

[@CODE_IS_EVERYTHING]

Ah good catch, not sure how I missed that.

[@Parker8752]

I did wonder why the /usr/bin/env was so common in scripts.

[@sphyrnidae6749]

🎉🎉🎉🎉

[@setsune999]

I need a tshirt with that thumbnail

[@senorchang6249]

What color Schema is that? Looks beautiful

[@CODE_IS_EVERYTHING]

I believe it is GitHub Dark.

[@flflflflflfl]

15:11 isn't it a convention to print (Y/n) with a capital Y only if "yes" is the default option if the user enters nothing (i.e., simply presses return)? Because your script would treat that as a "no", which could be confusing.

[@CODE_IS_EVERYTHING]

Good catch. You’re correct, I should’ve had it the other way around

[@rorylabine7143]

PLEASE make a hat with Bash Pro Shop on it. I would buy it so fast

[@CODE_IS_EVERYTHING]

Haha I’d love to but I imagine I’d be inviting trouble. But I’ll look into it.

[@user-hd3pz2ow1b]

co0l

[@dachanel2076]

whats the zshell interface/custom form you use? I'd love to try it.

[@CODE_IS_EVERYTHING]

I keep it pretty simple with just oh-my-zsh and then when I’m doing the video recording I set these export PROMPT='> ' export RPROMPT="" That way it gets rid of all of the extra noise. But on my day to day I don’t keep it like this since it gets rid of some useful info.

[@yaluvi7420]

😎😎

[@hanzomaster]

Can you pls tell me what is the font you use in this video? The # sign look so unique

[@CODE_IS_EVERYTHING]

I’m using IBM Plex Mono font for the code and Syne for the titles.

[@valeris98]

What font did you use btw?

[@CODE_IS_EVERYTHING]

For the code it is IBM Plex Mono. The titles are syne

[@KeithErekson]

How is hardcoding the path to "env" any better than hardcoding the path to "bash"?

[@CODE_IS_EVERYTHING]

It comes down to the portability. You have to hardcode some full path, but not every machine will have bash at the same location, whereas env is almost always at /usr/bin/env.

[@Vuden13]

What is your background?

[@CODE_IS_EVERYTHING]

I'm very much a generalist. Most of my "professional" career has been in the DevOps space, but I've been programming for over 15 years (though only half of that with any degree of skill lol) and I try and learn everything.

[@zawadhyaa]

what's that font?

[@CODE_IS_EVERYTHING]

The code font is ibm plex mono and the title font is syne

[@zawadhyaa]

@@CODE_IS_EVERYTHING thanks

[@hunterlake2943]

Still cant pass, AI voice over but great video! :)

[@CODE_IS_EVERYTHING]

Haha you think my voice is done by AI? 😅 Not sure how to take that. It is my real voice! But I'm glad you liked the video