With that in mind; his Lisp advice is terrible. After years of writing Lisp tutorials, he still hasn't actually learned it himself. Every time he comes up with a convoluted way to write something very simple in Lisp; and then formats it like he's writing C++. Very annoying. I ignore everything he says.
Both Visual Studio and Eclipse have these features, I'm sure there are many, many other editors and IDEs that also have them. It's not exactly rocket science.
If you want to champion Emacs, you might want to point out the features that really are unique and unmatched, instead of common features that everyone else implemented 10 years ago. Yes, yes, Emacs did it 20 years ago. Woo.
What makes Emacs so useful is not only what it has out of the box (it has a whole lot), but what it allows you to do with that. People often jokingly describe it as an operating system, but that's a surprisingly apt description. Everything in Emacs is accessible (most of it, anyway) and it is (a great part of it, at least) written in itself. To make a small function that searches for a, in this case, a booklike block, and replaces the classes with the proper ones is more or less a trivial task. I wouldn't use it for this case - it's too little work - but I would write a search-and-replace-with-option function that would highlight occurrences and offer me a menu of replacements.
If it doesn't exist in there already.
And that would also be a worthwhile exercise in IDE zen.
Contrast that with Eclipse or Visual Studio, where the job of writing extensions start to look like a whole career.
I use find and replace routinely with emacs, for tasks of many sizes, almost without thinking about it.
The only reason I use Emacs these days because it's the only decent freely available Common Lisp development environment (in conjunction with SLIME). In fact, I only use Emacs for Common Lisp. For everything else, there's vim / Eclipse / IntelliJ / Visual Studio.
Sounds like you need BeautifulSoup.
Emacs has macros & M-x spoon
I got all the way to the bottom before I realized his only point was that editing macros are cool.
It's one thing to rave about Emacs, it's another thing to actually show its power. A line of elisp would have been much more of an argument.