This was very stimulating and thoroughly enjoyable. It allowed me to understand how many of the subtleties I observed and experienced over the years come together.
01:56 Command Types 03:38 Getting Help 04:22 Some Useful Definitions 05:29 Return Status 06:42 Compound Commands 07:09 While and Until Loops 08:50 For and Select Loops 11:52 Tests 14:23 Conditionals: if 15:03 Pattern Matching 15:50 Conditionals: case 16:59 Command Groups 21:36 Redirection 22:11 Command and Process Substitution 23:09 Parameters 31:03 Arrays 33:50 Arithmetic Expansion 35:24 Brace Expansion 37:49 Functions 40:35 Session Portability
The best part of this whole video is right near the end showing the declaration of functions and parameters that can run on remote hosts. I knew about declaring functions in the current shell but this makes me want to convert some of my scripts to functions now just so I can run them on other hosts without having multiple copies of scripts all over the place. Awesome even eight years later.
I've been programing with Bash for two weeks, and even I can see just how powerful these tips are. I guess that the presentation was for advanced users, so I admit that the pace is far too fast for me right now, but that's the beauty of video. I can pause and take the information in, or code with the example onscreen, then unpause. Thank you for the knowledge!
Such wonderful things you have shared with us..even though video is relatively few minutes,took hours for me to gasp major content.. thanks for your effort
Well, maybe that is due to the 6 years that went inbetween, but these days theres quite a few situations where you won't have bash, I. E. when using a Docker container or an IOT device with a slim Linux. And even if you're on a full blown system better don't forget the shebang for bash if you use bashisms, as lots of people use I. E. zsh, including most people that use Mac OS as it's their default shell
He's probably referring to the extended globbing (extglob) patterns, and/or the ;& and &;; operators that allow multiple patterns to match the same input string.
is shell scripting this new that just in 2014 it had to be explained in an convention to me shellscripting or sql are simple english as long as u understand object and have the required laziness to automate . u can excel in this field.
I'm sorry, but I kept waiting for the promised "advanced" usages, yet all I got were the same old bog-standard features I've known about for ages. Loops, tests, functions, parameter expansions? What's advanced about those? Only the very last hint with *declare* was kind of new to me. I had never thought about using it in that way before. I suppose it will help some relative newcomers, and more power to them, I guess, but the title is a bit misleading. You'll learn much more reading the Bash FAQ and Bash Pitfalls pages at Greg's Wiki.
James, Really useful slides & well paced presentation! You mention "not logging into this account for some time", do you have another YT/Vimeo account where you host more material like this? It was really good.
Thank you! At the moment there's no other home for this stuff, I just don't spend much time logged into youtube. When/if I have more talks, www.jpnc.info/talks should be updated.
@@jamespannacciulli3029 James, I highly enjoyed your talk (I even learned a few neat tricks I haven't thought of). But please replace all those "echo" and "echo -e" with "printf" equivalents ^^ (let echo die... users should use printf. It will be much more consistent in its display, across shells and versions, and will be without several edge cases (printf "%s " "-anything starting with a minus", for exemple, will never barf. and lots of other related problems get avoided as well)
eventually, i released the scripts i made to pre-load my example commands as ariketa: git.jpnc.info/ariketa/about/ basically, i put all the examples ahead of time into an array in memory, using bind shortcuts to be able to quickly cycle through them as if they had been typed into the shell directly. i figure this saves time so that i can keep the pace up, while avoiding all the obligatory live demo typos. so something like "while read var1 var2; do echo $var2 $var1; done" would be loaded onto the command line when i cycled forward to that example from my array, then i would just type in the text like "one two" manually and the loop would return "two one" in that case. in case you are interested, i made a little write-up of my thinking and methodology here: www.jpnc.info/posts/en/2017/06/ariketa.yo/ hope that answers your question, sorry for the late response!
I found this video extremely useful. I am creating a cheatsheet based on the commands from this talk as practice and for future reference. You can find it on gist.github.com/projectivemotion/dc6f9b4e6241910c3d5c026a84988b7b
It's so sad to see GNU/Linux infection splitting through community. Hearing it being pronounced GNU/Linux feels so cringeworthy. What exactly do these people see is the benefit that they are bringing to the table to the world? I can't think of anything other than some salute a recognition towards GNU and FSF? I do respect them, but I do not respect their attempt to change what most world knows as Linux to some cumbersome GNU/Linux.
+EmperorTerran Tell us how you really feel. But seriously, why so sad about my having used the more complete, more accurate name for the OS? Although I do tend to casually refer to the OS as "Linux", I understand that this is taking a shortcut at the expense of somewhat misrepresenting the OS. It is actually ironic that I take this shortcut, as I am primarily interested in running a GNU OS, whether it were GNU/Linux, GNU/Herd, or GNU with some other free software licensed kernel. On the other side of that coin, I expect we should continue to see more OS's made combining the Linux kernel with non-GNU core libraries and programs, in which case the distinction between GNU/Linux and Linux without GNU, such as Android, becomes much more important. If I am giving a talk, I'll at least refer to the OS officially by what I consider to be its proper name, even if I may use the name "Linux" colloquially. Of course, I recognize that referring to it in this specific manner is also an implicit advertisement for the GNU project, and I definitely approve that message.
i am happy to hear 'GNU' such that i understand where i can use syntax/info as presented here. and delighted we have so many choices of distros which has made using this term is necessary
This was very stimulating and thoroughly enjoyable. It allowed me to understand how many of the subtleties I observed and experienced over the years come together.
I’ve seen a lot of bash tutorials. Your presentation may not be a tutorial, but it’s pedagogic gold.
01:56 Command Types
03:38 Getting Help
04:22 Some Useful Definitions
05:29 Return Status
06:42 Compound Commands
07:09 While and Until Loops
08:50 For and Select Loops
11:52 Tests
14:23 Conditionals: if
15:03 Pattern Matching
15:50 Conditionals: case
16:59 Command Groups
21:36 Redirection
22:11 Command and Process Substitution
23:09 Parameters
31:03 Arrays
33:50 Arithmetic Expansion
35:24 Brace Expansion
37:49 Functions
40:35 Session Portability
The best part of this whole video is right near the end showing the declaration of functions and parameters that can run on remote hosts. I knew about declaring functions in the current shell but this makes me want to convert some of my scripts to functions now just so I can run them on other hosts without having multiple copies of scripts all over the place. Awesome even eight years later.
I've been programing with Bash for two weeks, and even I can see just how powerful these tips are.
I guess that the presentation was for advanced users, so I admit that the pace is far too fast for me right now, but that's the beauty of video. I can pause and take the information in, or code with the example onscreen, then unpause. Thank you for the knowledge!
So much better than those conference talks that are marketing in disguise
Use "bc" (sudo apt install bc) for floating point arithmetic. Great talk.
This is a nice summary for all bash users and gives a great overview over its features. Well done!
Such wonderful things you have shared with us..even though video is relatively few minutes,took hours for me to gasp major content.. thanks for your effort
excellent presentation. thank you.
Very well presented ! Valuable information and Straight to the point
Thank you finally I found what I needed to understand some bash, before I was just copying stuff.
Such a nice presentation ! To the point & right on pace
29:43 o.O pointers in bash thats nice and i am for sure going to use 40:36 declaring own functions on remote hosts! Thats awesome thanks for the talk
This is so cool ! More advanced lecture would be awesome !!!
Saw it on reddit r/linux. This is really a great intro to bash.
Well, maybe that is due to the 6 years that went inbetween, but these days theres quite a few situations where you won't have bash, I. E. when using a Docker container or an IOT device with a slim Linux.
And even if you're on a full blown system better don't forget the shebang for bash if you use bashisms, as lots of people use I. E. zsh, including most people that use Mac OS as it's their default shell
16:10 what are those "recent additions" for more complex matching?
He's probably referring to the extended globbing (extglob) patterns, and/or the ;& and &;; operators that allow multiple patterns to match the same input string.
excellent presentation
is shell scripting this new
that just in 2014 it had to be explained in an convention
to me shellscripting or sql are simple english as long as u understand object and have the required laziness to automate . u can excel in this field.
Excellent video. Thank you.
I'm sorry, but I kept waiting for the promised "advanced" usages, yet all I got were the same old bog-standard features I've known about for ages. Loops, tests, functions, parameter expansions? What's advanced about those? Only the very last hint with *declare* was kind of new to me. I had never thought about using it in that way before.
I suppose it will help some relative newcomers, and more power to them, I guess, but the title is a bit misleading. You'll learn much more reading the Bash FAQ and Bash Pitfalls pages at Greg's Wiki.
I knew some of this stuff but not all of it.. we always have something to learn!😁
excellent. Hello James, I have a question, did you make your presentation in Latex o something else. I liked the syntax highlight ..
Great stuff for beginners in one shot.
Very nice presentation
James,
Really useful slides & well paced presentation!
You mention "not logging into this account for some time", do you have another YT/Vimeo account where you host more material like this? It was really good.
Thank you! At the moment there's no other home for this stuff, I just don't spend much time logged into youtube. When/if I have more talks, www.jpnc.info/talks should be updated.
@@jamespannacciulli3029 James, I highly enjoyed your talk (I even learned a few neat tricks I haven't thought of). But please replace all those "echo" and "echo -e" with "printf" equivalents ^^ (let echo die... users should use printf. It will be much more consistent in its display, across shells and versions, and will be without several edge cases (printf "%s
" "-anything starting with a minus", for exemple, will never barf. and lots of other related problems get avoided as well)
Thank you sir , great stuff.
question: the loop examples: is he loading them out of a file, or where does it come from? thanks in advance
eventually, i released the scripts i made to pre-load my example commands as ariketa:
git.jpnc.info/ariketa/about/
basically, i put all the examples ahead of time into an array in memory, using bind shortcuts to be able to quickly cycle through them as if they had been typed into the shell directly. i figure this saves time so that i can keep the pace up, while avoiding all the obligatory live demo typos. so something like "while read var1 var2; do echo $var2 $var1; done" would be loaded onto the command line when i cycled forward to that example from my array, then i would just type in the text like "one two" manually and the loop would return "two one" in that case.
in case you are interested, i made a little write-up of my thinking and methodology here:
www.jpnc.info/posts/en/2017/06/ariketa.yo/
hope that answers your question, sorry for the late response!
@@jamespannacciulli3029 Great way to teach!
James, slides link broken :(, would appreciate
found: cdn.oreillystatic.com/en/assets/1/event/115/Introduction%20to%20Advanced%20Bash%20Usage%20Presentation.pdf
+Martins Talbergs Sorry about that! Slides are back online at the link above in the video info.
so much content! thank you
Great vid. Thank you!
how to make a while loop in terminal?
thanks
type help its looking right at you
Declare knocked my socks off!
Thanks SIR!
nice, thank you
perfect
thanks.
👍👍
I found this video extremely useful. I am creating a cheatsheet based on the commands from this talk as practice and for future reference. You can find it on gist.github.com/projectivemotion/dc6f9b4e6241910c3d5c026a84988b7b
Gracias!
🔥🔥
Holy shit
Great presentation. Although his delivery is just like the comedian Steven Wright, which is funny, because he isn't.
This is why people hate Linux. On the other hand this is why nerds love Linux! :)
cd HAS a man page
It's so sad to see GNU/Linux infection splitting through community. Hearing it being pronounced GNU/Linux feels so cringeworthy. What exactly do these people see is the benefit that they are bringing to the table to the world? I can't think of anything other than some salute a recognition towards GNU and FSF? I do respect them, but I do not respect their attempt to change what most world knows as Linux to some cumbersome GNU/Linux.
+EmperorTerran Tell us how you really feel. But seriously, why so sad about my having used the more complete, more accurate name for the OS? Although I do tend to casually refer to the OS as "Linux", I understand that this is taking a shortcut at the expense of somewhat misrepresenting the OS. It is actually ironic that I take this shortcut, as I am primarily interested in running a GNU OS, whether it were GNU/Linux, GNU/Herd, or GNU with some other free software licensed kernel. On the other side of that coin, I expect we should continue to see more OS's made combining the Linux kernel with non-GNU core libraries and programs, in which case the distinction between GNU/Linux and Linux without GNU, such as Android, becomes much more important.
If I am giving a talk, I'll at least refer to the OS officially by what I consider to be its proper name, even if I may use the name "Linux" colloquially. Of course, I recognize that referring to it in this specific manner is also an implicit advertisement for the GNU project, and I definitely approve that message.
i am happy to hear 'GNU' such that i understand where i can use syntax/info as presented here. and delighted we have so many choices of distros which has made using this term is necessary
I just use freebsd. much better :)
"advanced"
Yea i would also consider most of it basic but some things were still new to me :)
He had to go through the basics, but it got advanced towards the end and some stuff was new to me.