Incredible. I wish all tutorials were this clear and concise. You go from blackboard teaching to ACTUAL coding and break it down piece by piece. Not copy-pasting code with barely any explanation of what is going on within the code. Keep it up, Jason!
8:56 > _"color coded command line is we can actually see [matches]"_ for those wondering, it actually is achieved by doing this (if wanted persistently, then in the bashrc file): alias grep='grep --color'
I had been searching for something that would explain grep, sed, and regular expression for so long, and no resource made much sense, but you made everything so clear and easy to understand. Thanks so much :)
Thanks a lot! I'm studying for the CompTIA Linux exam and I have trouble understanding regular expressions. I'm gonna practice a lot, your video made it much easier to understand.
Very informative tutorial..I was giving a practice mock interview to my husband and i could answer most of the questions correct. Thanks man. bless you
grep stands for g/re/p which is the basic pattern form where 'g' means 'global' (not 'get'), 're' means regular expression and 'p' means print. This goes back to the early days of Unix before even System V I believe.
7:45 We'll use grep until it breaks (and then we'll use egrep). 9:21 Put double quotes to avoid some non-standard character of our regex being interpreted by the shell like actually shouldn't. 34:06 The sed command filters daa for editing.
Just installed Linux subsystem and found this very helpful, because I used for number of years 'Windows' , didn't know to type single command in a shell, okay maybe some. Some commands match - some not at all. Thank you. * I have to mention since Ii use linux scripts I see better staff on a monitor! :) + there is a couple more sites in a search experience.
jason, im sorry if i didnt express it b4, but i love you!! im sorry i meant you,ve opened my mind about regex. i really really apprecite this pal. thanks for helping people like i. God bless you bro :)
Thanks, even after few years i love to still learn stuff. Suggestion: maybe have the files you use in the examples available somewhere (put them online somewhere then archive with internet archive to make sure they are available forever)
Very good tutorial.Thank you! Just one question: Is there anything wrong if I surround my pattern with double quotes even if I don't use some special characters?
When you wc -w some text of exactly 1000 words you get 1000 as a result. However when you split the same text with grep into individual words you get 1040 words because grep is splitting off the ‘s and ‘t from words like • he’s • there’s • don’t • won’t • etc. when you do • cat input_file | grep -oE '\w{1,} ' Is there a way to make grep behave like wc, or do we have to use a different strategy for getting the right (desired) result? Any ideas?
Great video! My only suggestion would be to pick one standard and stay with it. Example, only teach the "[0-9][a-z]" stuff. Don't include examples with the "/d /w" stuff. It just confused me.
Very nice video! I want my file to have the project name and version. How do you this with mv? I dont have and cannot install rename. mv project-3.2-jar-with-dependencies.jar ??????? goal: project-3.2.jar
Incredible. I wish all tutorials were this clear and concise. You go from blackboard teaching to ACTUAL coding and break it down piece by piece. Not copy-pasting code with barely any explanation of what is going on within the code. Keep it up, Jason!
8:56 > _"color coded command line is we can actually see [matches]"_
for those wondering, it actually is achieved by doing this (if wanted persistently, then in the bashrc file): alias grep='grep --color'
literally , the best straight to the point tutorial soo far
Seriously, man, you should become a teacher. Much thanks.
grep stands for '-g-lobally search for a -r-egular -e-xpression and -p-rint out matched lines'.
Wow thanks
Best video on regexp, clean and concise, thankyou very much!!
You are the best teacher ever, simple and to the point. If you were a girl I would have kissed you.
Thumbs up. Thanks to people like you, people are able to get smarter in computer science.
Hey I just spent 30 worth while minutes practicing Regular Expressions. well compiled lecture. Thank you Jason
Helped me so much. Taking an online course with no videos and this just saved me.
I had been searching for something that would explain grep, sed, and regular expression for so long, and no resource made much sense, but you made everything so clear and easy to understand. Thanks so much :)
One of the best tutorials in Linux
Thanks a lot for this lesson, I was afraid of even getting started with learning RegEx and this video helped me remove those fears.
This video series is one of the best I've ever seen. Thanks so much for your approach. Hope to see more someday!
Thanks jason... Well compiled and explained tutorial. Cleared many of my doubts on regular exp... Many thanks
Thanks a lot! I'm studying for the CompTIA Linux exam and I have trouble understanding regular expressions. I'm gonna practice a lot, your video made it much easier to understand.
It's a very informative and perfect video for those who don't know anything about regex.
Concise,Clear,To the point
Sir you are too good...the way you teach is amazing. Very precise and to the point.
Amazing amazing tutorial!! Anytime I forget grep I will come back here. Many thanks!!
You sir are one hell of a teacher!!
Very informative tutorial..I was giving a practice mock interview to my husband and i could answer most of the questions correct. Thanks man. bless you
Thanks Jason , really cleared most of the things in on Reg-ex. really appreciate your time on this..
Just a magnificent teacher. Thx from Argentina my friend!
Beautifully done. Thanks so much for sharing your expertise. Totally worth watching.
The perfect explanation I wish you were my professor.
Jason. Your video on REX is really helpful, really appreciate it.
Thank you so much for this great video👍👍👍
Please keep doing this.!!!!!!!!!!!!!!!!!!!
Thank you Sr.!!
Thanks. This is very helpful, to understand the basic concept of regex.
grep stands for g/re/p which is the basic pattern form where 'g' means 'global' (not 'get'), 're' means regular expression and 'p' means print. This goes back to the early days of Unix before even System V I believe.
There is a Computerphile video with Brian Kernighan talking about this.
Thank you for the lesson, just what I needed! Very well done Sir!
Thank you, this helped a lot. Truly awesome.
7:45 We'll use grep until it breaks (and then we'll use egrep).
9:21 Put double quotes to avoid some non-standard character of our regex being interpreted by the shell like actually shouldn't.
34:06 The sed command filters daa for editing.
Very good video. Well done.
Just installed Linux subsystem and found this very helpful, because I used for number of years 'Windows' , didn't know to type single command in a shell, okay maybe some. Some commands match - some not at all. Thank you. * I have to mention since Ii use linux scripts I see better staff on a monitor! :) + there is a couple more sites in a search experience.
Amazing lesson Jason. Well done I will subscribe and give you thumbs up. Well done loved it
Really excellent work. It helped me a lot...
30:59 curly brackets are parrt of the extended grep. POINT NOTED
Really struggling with regex for some reason, but your tutorial is helping!
This was really good. Thanks for this.
Thank you sooOOO much Jason! good stuff here.
jason, im sorry if i didnt express it b4, but i love you!! im sorry i meant you,ve opened my mind about regex. i really really apprecite this pal. thanks for helping people like i. God bless you bro :)
This is really a good vid. I stopped at the half way point, but plan to continue tomorrow. Thanks for sharing.
Why this playlist has stopped in between. We want a whole playlist with more videos on Linux kernel. You are such an awesome teacher :0
WOW Nice Lecture!!
Great video, thank you
amazing video, thank you
great video...
A doctor who fan right there.
Very good video even though it's an oldie. It would be so great to have an update on this with more of sed and awk :-p
I wonder if there is an advantage in using "-P", the perl-like regexes with grep.
nice tutorial! thanks
16:57 > _"\d Not standard in grep"_
aahhhhh!!! msys2's GNU grep 3.0 doesn't has this :)
THANKS A LOT HOMIE
Another though. if we use webscraping or wget the entire page, just above the buffer saved. we can regex the entire source for emails
I still wonder why there is no abbreviated character class for vowels, like [[:vowel:]]
very concise and helpful
AWESOME!
thank you so much really amazing
Thanks, even after few years i love to still learn stuff. Suggestion: maybe have the files you use in the examples available somewhere (put them online somewhere then archive with internet archive to make sure they are available forever)
Is there a CLI dictionary available for Mac Terminal?
Thankyou for this.
thanks a lot !!
Nice content
Thanks
Thank you! This video was helpful :)
Go Jason go Jason!!!!
How could I grep email addresses and simply return the domain name part behind the “@“?
Only one "complaint" a backslash is not a slash. ;)
Very good tutorial.Thank you! Just one question: Is there anything wrong if I surround my pattern with double quotes even if I don't use some special characters?
👍👍👍👍👍👍
nice.
Do you have any advanced Sed tutorials? The web is overflowing with intros and basics
When you wc -w some text of exactly 1000 words you get 1000 as a result. However when you split the same text with grep into individual words you get 1040 words because grep is splitting off the ‘s and ‘t from words like
• he’s
• there’s
• don’t
• won’t
• etc.
when you do
• cat input_file | grep -oE '\w{1,} '
Is there a way to make grep behave like wc, or do we have to use a different strategy for getting the right (desired) result?
Any ideas?
Are you usually a trainger? You got great tone, vibe and way. Thank you for this :D
Why was it necessary to keep $ at the end of the email and ^ at the start ? Will it not work with those characters ?
where could find my dictionary in centos 7-x86
cool voice
Great video! My only suggestion would be to pick one standard and stay with it. Example, only teach the "[0-9][a-z]" stuff. Don't include examples with the "/d /w" stuff. It just confused me.
Can anyone help me to give numbers not alphanumericals
dog - dog = dog
ok got it
Kang bli ngerti ngacung bae...
so the sed command doesn't change the real file, only give you the results with the replaced item you asked for.
sed does the change but an option of -e has to be specified before.
+nasir ali flad of -i to be corrected
Very nice video!
I want my file to have the project name and version. How do you this with mv? I dont have and cannot install rename.
mv project-3.2-jar-with-dependencies.jar ???????
goal: project-3.2.jar
I guess we can use awk language. The spectrum would be wide!!
]
You can pull this to ur github and add it to video for further references :
github.com/zeeshanu/learn-regex
I would turn into gay just to marry you, very good video!!
Grap "//d" /path/