Context
I have been using Vim for more than 6 years and have compiled it from source a couple of times during that period. Over the years my vimrc
did grow. Now, I am trying to clean my vimrc
and I came upon a dinosaur configuration: has("autocmd")
.
When I started using Vim I copied my first vimrc
from a colleague and it already contained a condition with a call to has("autocmd")
, as follows:
if has("autocmd")
" ... several autocmds, most of them on the FileType event
endif
Vim (likely) can be compiled without autocmd
support, and, I believe, during those days it was still possible to find a Vim instance without autocmd
support.
Over the years some 60-70% of my vimrc
migrated into that if
block, and now that block is huge (300+ lines). If I run a Vim without autocmd
support I'll lose the majority of my vimrc
.
On the other hand, I believe that has("autocmd")
is rather irrelevant these days. And, therefore, I want to get rid of that if
altogether.
I looked through Vim's configure.in
and there is no way to explicitly disable autocmd
in there. Looking through neovim
's source tree I do not see an Find*
cmake for autocmd
either, I do not believe that neovim
can be compiled without autocmd
.
The Question
Since "relevance" is a rather opinionated topic, let's focus on the objective points of has("autocmd")
:
Under which conditions Vim can be/is compiled without
autocmd
support?Are there official compiled packages/distribution of Vim without
autocmd
support? (Maybe on embedded devices)Both questions above but for
neovim
.
if 1
is more useful in this case. – Antony Jul 4 '16 at 0:30neovim
people have done when they forked Vim was to drop support for all build modes excepthuge
, and for targets such as Commodore Amiga and the like. – Sato Katsura Jul 4 '16 at 5:41