This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [RFC] vim-minimal in Base?
- From: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 20 May 2013 03:25:24 -0500
- Subject: Re: [RFC] vim-minimal in Base?
- References: <5191AF60 dot 3030305 at users dot sourceforge dot net> <5191E2A4 dot 9010305 at etr-usa dot com> <20130514075946 dot GA23074 at calimero dot vinschen dot de> <51920568 dot 1000102 at users dot sourceforge dot net> <20130514112705 dot GA5737 at calimero dot vinschen dot de>
On 2013-05-14 06:27, Corinna Vinschen wrote:
Er... what? Since when does syntax highlighting require perl?
Not directly: syntax highlighting requires files from vim-common, which
pulls in perl due to other perl scripts contained therein.
The old vim package I compiled when I maintained it was built with the
--with-features=huge setting but didn't pull in any of the possible
dependencies. No perl, no python, no ruby. But syntax highlighting
worked fine.
The vim package still provides the huge feature set, now with the
addition of lua/perl/python/python3/ruby support (dynamically loaded).
Basically, if you want features, keep using vim. Otherwise, ex/vi
(vim-minimal) provides the basic POSIX functionality. The big change is
that vi != vim anymore.
Apart from that, I guess calling vi (and that's what *many* users are
used to) will now result in the same error Frank reported.
The workaround will be to use ~/.virc with vi.
Any chance to build vim-minimal with a bigger default set of features
which is only based on avoiding external deps?
The bigger feature sets require the support files in vim-common, and
*that* is the dependency which needs to be avoided for a minimal,
Base-worthy ex/vi.
Yaakov