1. 17

  2. 2

    Wow, this article and the previous one are very convincing. I’ve used Vim forever (technically Neovim nowadays), both in school and at work, but now I want to give Emacs a try.

    Has anyone achieved something similar with Vim, plugins, and peripheral programs a la Unix as IDE? Or am I better off switching to Emacs?

    1. 3

      My personal opinion: I think you’re going to have an easier time with this kind of work in Emacs than in Vim. Emacs has a much wider variety of tools for doing things outside of simply manipulating text. But of course, the idea with Vim is to outsource that kind of stuff to other terminal programs. That strategy usually works better than shoehorning functionality into Vim with Vimscript.

      Vim combined with terminal utilities for mail, scheduling, etc. are probably going to be more stable and easy-to-use from the start, but Emacs gives you a more integrated way to access those tools and an easier way to customize them.

      If you do want to use Emacs, I’d try Evil. I’m still not sure on which side of the fence I personally end up; lately I’ve been getting annoyed with how temperamental Emacs can be with conflicting packages and a complicated configuration, but at the same time Vimscript is a special kind of horrible.

      Really, I think the editor war boils down to convention vs configuration, or better termed curation over configuration. Using vanilla Emacs is painful; configuring Vim to be an “IDE” is painful.