Vim不是一个壳。而且它不能很好地与子进程通信。这几乎是设计的，而在Emacs中，这些元素是设计包含的。这意味着有些东西，比如嵌入调试器或解释器(产生某种IDE)，在Vim中是很困难的。

此外，Emacs快捷方式主要是通过修饰符访问的，显然Vim接口是出了名的模态接口，可以访问大量的直接键进行操作。

Emacs曾经是这两个编辑器中唯一可编程的编辑器，而Vim的可编程性有很多奇怪的级别，添加了Python和Ruby绑定(还有更多，我忘记了)，Vim也可以以您所关心的大多数方式进行可编程。

我使用Vim，而且我对它相当满意。

If you are looking for an objective analysis of both the editors, look at their origins and the philosophy behind their respective designs. Think, which one would suit you better and learn it (and learn it and learn it, because it takes time before you being to discover its true utility as against any IDE). An Introduction to Display Editing with Vi was written by Bill Joy and Mark Horton and he explains why he choose modal design and rationale for various key strokes ( it helps me to remember that CTRL-W +W (will switch to next Window and it will same for CTRL W+ CTRL W, just in case you held the CTRL key for a longer duration.

这里有一个Emacs时间轴的链接，并有对Multics Emacs论文的参考。这是一篇关于Emacs的RMS论文，我看到重点在可编程文本编辑器上(甚至早在1981年或更早的时候)。

我没有读过emacs的论文，但是读过Bill Joy的vi论文几次。 两者都是旧的，但你仍然会得到哲学，你可以选择使用当前的工具(vim 7。X还是emacs 25?)

编辑:我忘了说，阅读这两篇论文需要耐心和想象力，因为它会让你在阅读时回到过去。但这是值得的。

Emacs具有Viper模式，因此在某种意义上，它提供了一个超特性集(除了那些在使用Viper和Vimpulse的Emacs中缺少哪些Vim特性?)

vi(和VIM IIRC)的重量较轻(它可以就地编辑文件)，但提供的功能较少(子进程通信、扩展语言)。

Vim是一个方便的编辑器，你只需输入Vim的文件名来打开文件，编辑，保存和关闭。

Emacs是一个伪装成编辑器的“操作系统”，你可以评估代码来改变它的行为，并按你的喜好扩展它。在emacs上接收/发送电子邮件的模式类似于操作系统上的电子邮件软件。

当进行简单的编辑时，例如，修改配置文件，我使用vim。

否则，我永远不会离开emacs。

Emacs的好处

Emacs has both non-modal interface (by default) and modal one (e.g. it can emulate vim and vi through Evil, Viper, or Vimpulse). One of the most ported computer programs. It runs in text mode and under graphical user interfaces on a wide variety of operating systems, including most Unix-like systems (Linux, the various BSDs, Solaris, AIX, IRIX, macOSetc.), MS-DOS, Microsoft Windows, AmigaOS, and OpenVMS. Unix systems, both free and proprietary, frequently provide Emacs bundled with the operating system. Emacs server architecture allows multiple clients to attach to the same Emacs instance and share the buffer list, kill ring, undo history and other state. Pervasive online help system with keybindings, functions and commands documented on the fly. Extensible and customizable Lisp programming language variant (Emacs Lisp), with features that include: A powerful and extensible file manager (dired), integrated debugger, and a large set of development and other tools. Having every command be an Emacs Lisp function enables commands to DWIM (Do What I Mean) by programmatically responding to past actions and document state. For example, a switch-or-split-window command could switch to another window if one exists, or create one if needed. This cuts down on the number of keystrokes and commands a user must remember. "An OS inside an OS". Emacs Lisp enables Emacs to be programmed far beyond editing features. Even a base install contains several dozen applications, including two web browsers, news readers, several mail agents, four IRC clients, a version of ELIZA, and a variety of games. All of these applications are available anywhere Emacs runs, with the same user interface and functionality. Starting with version 24, Emacs includes a package manager, making it easy to install additional applications including alternate web browsers, EMMS (Emacs Multimedia System), and more. Also available are numerous packages for programming, including some targeted at specific language/library combinations or coding styles.

vi类编辑器的好处

Edit commands are composable Vi has a modal interface (which Emacs can emulate) Historically, vi loads faster than Emacs. While deeply associated with UNIX tradition, it runs on all systems that can implement the standard C library, including UNIX, Linux, AmigaOS, DOS, Windows, Mac, BeOS, OpenVMS, IRIX, AIX, HP-UX, BSD and POSIX-compliant systems. Extensible and customizable through Vim script or APIs for interpreted languages such as Python, Ruby, Perl, and Lua Ubiquitous. Essentially all Unix and Unix-like systems come with vi (or a variant) built-in. Vi (and ex, but not vim) is specified in the POSIX standard. System rescue environments, embedded systems (notably those with busybox) and other constrained environments often include vi, but not emacs.

来源:https://en.wikipedia.org/wiki/Editor_war

偏颇的观点:

Vi(不是vim)是一种专业需要。你总是有某种形式的 Vi容易获得，无论什么环境。你可以在vi中 在emacs中，您可以在vi中在unix-land中构建bash命令。

甚至Microsquish也必须支持vi(尽管他们做得很好 隐藏它)，因为政府和公司遵守公布 标准。

在我看来，如果你在一个繁忙的环境中从事一份亲力亲为的工作——不 温室里的一朵花，被限制在一个开发项目的一个花哨的钻机上 环境，或者在学术界——了解一个高级编辑是一项工作 障碍。不要学习vim或emacs中的所有花哨技巧，不要 开发一堆宏，使编辑环境屈从于你的意愿。 这是一个巨大的时间消耗，当你注意的时候 不同的机器，你可能不能证明在工厂 环境。

读读比尔·乔伊的论文，他写得很好，甚至可以说 非常漂亮，编辑纯文本的工程练习 快。帕里托法则适用于此:80%的水果都在20%里 篮子的。编辑纯文本非常非常快是关键 编辑能力——其他都是可选的——有时是有害的。