Honestly, it is still beyond me why do you have only ~550 subscriptions. Your videos are great, in-depth and entertaining :) Keep up the great work, Robert! Looking forward for your next video :) Stay safe, mate!
Wonderful explanation, and the first video I've seen where the name 'ed' is pronounced correctly! Like ex and vi, you just say the letters. Last year I decided to keep things simple and now ed is my primary command-line editor. I like the way it doesn't take over my terminal display the way vim and Emacs (and for that matter nano) do. it's simple and powerful, launches quickly, and exits cleanly. Some people say it's fine for small files but they wouldn't want to have to use it for longer texts. I remind them that actually most of Unix was written with it.
Today I started to learn ed, and I find it very fascinating, specifically because it is a editor how you were required to operate back in the time. It really does take lot of thinking at first, but once you get through basics, it becomes fancy effective tool. I started reading IBM man pages about it, that explained the basics, as how to start new file, how to appendix to existing file, how to find wanted lines etc. And all the time I was wishing that I would have a matrix printer to use as a terminal output. Especially in this video the "stty -echo" was real revelation that got me wake up. As well I haven't for years used the "info", not even the man pages anymore, as I usually just check the --help and if there is nothing then I jump to google. Today I as well found a new editor to replace nano, called "micro". It is pretty huge in size (4MB) and it is made to common users in mind, by offering the ctrl+s and ctrl+z etc shortcuts from common GUI use. Only feature I found interesting with it was the tabs, that you can open multiple buffers as own tabs inside the micro, and jump quickly between them. This allows easily to example have sample file and edited file open and copy-paste text between. Another nice quick feature was easy way to push micro on background and run some command and then after it is ended, return to micro as is. But back to ed, and it is very refreshing to be so... simple. With a little practice it becomes comfortable to use. I didn't know where to find all the possible commands, why it was slight surprise that in this video the "1,$p" did what I was searching for in first time. As when you start with new file, you can easily constantly keep track what you have written. But opening existing file, and you need to start from first line and just print all with Enter key to the end. So the command is easy to understand "first line, to end, print". So no more exit and cat to see what was there in full (or using that enter mentioned). Now when I just would find is there way to have line numbering visible on the left as it would make even easier the thing.
I use ed every day. It's specified as my git editor. That way I can do my commits, rebases and reverts in the same terminal window that I'm already working in, without it being all taken up by vi, and can still see previous commands
Back in the days when an operating system was needed for the first Personal Computer, MicroSoft made a cheap'n'nasty hack of producing a single-user, single-task version of Unix and called it Disk Operating System (DOS). For copyright reasons they had to change all kinds of command names. Ed became "edlin" in DOS, and I used to love using it, because it was fast and incredibly cool and geeky when others were watching. 😎👍
I had to write FORTRAN, actually WATFIV an implementation of FORTRAN developed at the University of Waterloo, using "smart" terminals with the programmes sent to a mainframe to be executed, and wait for the print-out sheet(s) to be deposited in the slot with the same number as had been displayed on the terminal screen. A few years earlier, it was punch cards that had to be taken to the computer operator's window to be loaded into the mainframe, and wait for the results.
Learning more everyday. Thank you! Now I also understand better how everything works perfectly over an SSH terminal session for example (bash, vim, nano, all of it, completely with colors and correct coordinates, even when I resize the terminal emulator window). It's all just the exchange of that ANSI escape sequences that does the whole magic. Can we also call it a protocol? It also reminds me me a bit of today's HTTP protocol and HTML language in the sense of remote communication in combination with the concept of a markup language. It's the client (the browser) that renders everything grapically, but HTTP communication itself goes in both directions, especially with the web APIs of today.
the manpage for ed is significantly more informative on a BSD system than on a GNU system. the commands and addressing modes are actually detailed! the GNU project just hates manpages
Ed's actually extremely useful when you've derped up your terminal or are unable to use control keys (When `esc` isn't usable, neither are Vi/Vim.). Line editors also require a rather fun way of thinking, and Ed, in particular, makes `sed` and `grep` make much more sense.
Frnd pulled a prank on me ed on autostart after boot 😑 now had to find out how to exit. Digging out "?" Is ed output was the first step. Ty q enter worked. 🙈
There are some teachers who have their students write code on paper. Now I wonder if that exists because the teachers of their teachers' teachers actually coded in the 60s/70s, where you would want to write your code out on paper first, because it would have been a pain to try to find and fix your mistakes using ed.
Weirdly enough, one time I had to edit a few GBs file, can't remember why or what it is.... VIM wouldn't open it.. and the weird part ( ed ) couldn't open it either, thats when I knew that even ed loads file into memory... only `less` was able to load the file, and using its command mode, redirecting lines to vim, editing there, and saving that I was able to edit a huge file without loading all of it in memory.... ( not sure why I couldn't use sed .. that was few years back )
Yup. The previous version that I uploaded had some issues with volume normalization and I kept getting comments about how it was a great video, but the audio ruined it so I deleted the old version and uploaded a new one with the audio fixed.
“I want an EDitor! Not a ‘viitor’! Not an ‘emacsitor’! Those aren’t even WORDS!”
@@kreuner11 It is.
ed man! !man ed
Your demo model was so creative and effective! I'll never forget it!
Because of this video and your shorts I have become a Patreon member! Somehow you manage to be fun, educational, and engaging.
God love you!
Honestly, it is still beyond me why do you have only ~550 subscriptions. Your videos are great, in-depth and entertaining :)
Keep up the great work, Robert! Looking forward for your next video :) Stay safe, mate!
Thanks for the kind words :)
Didn't planned to spend more than 10 seconds but ended up staying up to whole video. Your explanations are engaging.
Wonderful explanation, and the first video I've seen where the name 'ed' is pronounced correctly!
Like ex and vi, you just say the letters.
Last year I decided to keep things simple and now ed is my primary command-line editor.
I like the way it doesn't take over my terminal display the way vim and Emacs (and for that matter nano) do.
it's simple and powerful, launches quickly, and exits cleanly.
Some people say it's fine for small files but they wouldn't want to have to use it for longer texts.
I remind them that actually most of Unix was written with it.
Today I started to learn ed, and I find it very fascinating, specifically because it is a editor how you were required to operate back in the time.
It really does take lot of thinking at first, but once you get through basics, it becomes fancy effective tool.
I started reading IBM man pages about it, that explained the basics, as how to start new file, how to appendix to existing file, how to find wanted lines etc.
And all the time I was wishing that I would have a matrix printer to use as a terminal output.
Especially in this video the "stty -echo" was real revelation that got me wake up.
As well I haven't for years used the "info", not even the man pages anymore, as I usually just check the --help and if there is nothing then I jump to google.
Today I as well found a new editor to replace nano, called "micro". It is pretty huge in size (4MB) and it is made to common users in mind, by offering the ctrl+s and ctrl+z etc shortcuts from common GUI use.
Only feature I found interesting with it was the tabs, that you can open multiple buffers as own tabs inside the micro, and jump quickly between them. This allows easily to example have sample file and edited file open and copy-paste text between.
Another nice quick feature was easy way to push micro on background and run some command and then after it is ended, return to micro as is.
But back to ed, and it is very refreshing to be so... simple. With a little practice it becomes comfortable to use.
I didn't know where to find all the possible commands, why it was slight surprise that in this video the "1,$p" did what I was searching for in first time. As when you start with new file, you can easily constantly keep track what you have written. But opening existing file, and you need to start from first line and just print all with Enter key to the end.
So the command is easy to understand "first line, to end, print".
So no more exit and cat to see what was there in full (or using that enter mentioned).
Now when I just would find is there way to have line numbering visible on the left as it would make even easier the thing.
Great video! It's hard to find such engaging content on niche things like these
Great video. Always wondered how terminals worked.
Finally a good quality content about UNIX tools, subbed.
I use ed every day. It's specified as my git editor. That way I can do my commits, rebases and reverts in the same terminal window that I'm already working in, without it being all taken up by vi, and can still see previous commands
Back in the days when an operating system was needed for the first Personal Computer, MicroSoft made a cheap'n'nasty hack of producing a single-user, single-task version of Unix and called it Disk Operating System (DOS). For copyright reasons they had to change all kinds of command names. Ed became "edlin" in DOS, and I used to love using it, because it was fast and incredibly cool and geeky when others were watching. 😎👍
I used this in university a few years 😁 ago. Imagine writing a Fortran program with this.
I had to write FORTRAN, actually WATFIV an implementation of FORTRAN developed at the University of Waterloo, using "smart" terminals with the programmes sent to a mainframe to be executed, and wait for the print-out sheet(s) to be deposited in the slot with the same number as had been displayed on the terminal screen. A few years earlier, it was punch cards that had to be taken to the computer operator's window to be loaded into the mainframe, and wait for the results.
Line editors are underrated.
Very instructive and interesting stuff.
Learning more everyday. Thank you! Now I also understand better how everything works perfectly over an SSH terminal session for example (bash, vim, nano, all of it, completely with colors and correct coordinates, even when I resize the terminal emulator window). It's all just the exchange of that ANSI escape sequences that does the whole magic.
Can we also call it a protocol?
It also reminds me me a bit of today's HTTP protocol and HTML language in the sense of remote communication in combination with the concept of a markup language. It's the client (the browser) that renders everything grapically, but HTTP communication itself goes in both directions, especially with the web APIs of today.
the manpage for ed is significantly more informative on a BSD system than on a GNU system. the commands and addressing modes are actually detailed! the GNU project just hates manpages
Excellent video! And you even pronounced it right!
Ed's actually extremely useful when you've derped up your terminal or are unable to use control keys (When `esc` isn't usable, neither are Vi/Vim.). Line editors also require a rather fun way of thinking, and Ed, in particular, makes `sed` and `grep` make much more sense.
Excellent video. Subscribed.
This is great. Pls make more videos.
Thank you for the video, it's helpful and interesting.
Glad you enjoyed it!
Great video! Subscribed
Thanks for sharing.Good stuff 👍
Great explanation
Frnd pulled a prank on me ed on autostart after boot 😑 now had to find out how to exit. Digging out "?" Is ed output was the first step.
Ty q enter worked. 🙈
MS-DOS had a similar command/utility called edlin.
Yeah, but did edlin make such powerful use of regular expressions as ed does?
@@lorensims4846 not to my knowledge; as far as I recall edlin had not support for regex - it was a primitive line editor.
There are some teachers who have their students write code on paper. Now I wonder if that exists because the teachers of their teachers' teachers actually coded in the 60s/70s, where you would want to write your code out on paper first, because it would have been a pain to try to find and fix your mistakes using ed.
Weirdly enough, one time I had to edit a few GBs file, can't remember why or what it is.... VIM wouldn't open it.. and the weird part ( ed ) couldn't open it either, thats when I knew that even ed loads file into memory... only `less` was able to load the file, and using its command mode, redirecting lines to vim, editing there, and saving that I was able to edit a huge file without loading all of it in memory.... ( not sure why I couldn't use sed .. that was few years back )
Nice video! subscribed
wow what a nice channel!
Ed is the standard text editor.
you need to add silly thumbnails and then you're gonna have much more subs ;)
haha yeah, I'm working on it. I plan to gradually amp up the thumbnails as I learn more about the audience.
What? Didn't you already have this exact same video?
Yup. The previous version that I uploaded had some issues with volume normalization and I kept getting comments about how it was a great video, but the audio ruined it so I deleted the old version and uploaded a new one with the audio fixed.
What's wrong with echo and cat? , >>, and all
Those work too :)
Difficult to change text or add something before the first line.
@@lorensims4846 echo "something" > /tmp/newfile.txt && cat firstlinefile.txt >> /tmp/newfile.txt
Why not just use `dd`?
and I thought Vim was difficult...