5 ms·
I took a bit of time learning how to use Vim macros a few years ago, and then never envied SublimeText programmers again. The fact that I could compose and stor
by tombert 9y ago
I took a bit of time learning how to use Vim macros a few years ago, and then never envied SublimeText programmers again. The fact that I could compose and store the macros meant that I can effectively augment the editor without having to muck about with Python, Vimscript, or Emacs Lisp.
- gumby 9y agoYou can save emacs macros in a file as well. No need to rewrite them in emacs lisp. This feature has existed in Emacs since before GNU Emacs.
- tombert 9y agoOh, I wasn't trying to say that you can't do that in Emacs, I just never learned how to use them. I wasn't trying to knock Emacs macros in this case, I was just saying that once I learned Vim macros, I realized that it eliminated a lot of my previous cases where I had to muck about with the editor's scripting language.
- kryptiskt 9y agoEmacs = Editor MACroS It started out as bunch of TECO macros.
- gumby 9y agoThey were, but programming in TECO (although they were just strings of edit commands) was more complex than emacs lisp, believe me. I wrote a lot of MIT TECO back in the day and don't miss it!
- todd8 9y agoThinking back, its hard to believe that I spent a fair amount of time teaching students the ins and outs of TECO because that was a more effective way to do the coding required in my class. The alternative was punching cards. It was a second semester university course for CS students.