3 ms·
I too fit that description for some time. Vim is what I would use when starting an editor to do something to a file, and emacs when wanting to live in the edito
by sls 11y ago
I too fit that description for some time. Vim is what I would use when starting an editor to do something to a file, and emacs when wanting to live in the editor and reach out to external tools like a repl for some extended time.
Using emacs in daemon mode with launchctl on osx and then making a shell alias and an automator launcher for emacsclient that just connects makes starting the new client so fast that I can use emacs for the quick jobs, too. The only thing I have to do now is get used to the emacs command equivalents for the quick edit jobs. For example, in vim I can open a file to a specific line, delete that line and then the first 5 characters of the next 50 lines, and exit the editor in just a few keystrokes, while in emacs I'd still be playing with C-h a and googling. The things I've spent the most time in emacs doing, common lisp, clojure, latex, and so on, have a very different set of common operations than the common sysadmin tasks I used vim for.