On 2013-05-14 05:19, Frank Fesevur wrote:
It overrides the symlink from vi to vim.exe and so this breaks my
current setup:
$ vi
Error detected while processing /home/Frank/.vimrc:
line1:
E319: Sorry, the command is not available in this version: syntax on
Press ENTER or type command to
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
2013/5/20 Yaakov (Cygwin/X):
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
On 5/13/2013 21:28, Yaakov (Cygwin/X) wrote:
As these utilities are required by
POSIX[1], should the vim-minimal package be added to Base?
As long as when I install vim-kitchensink setup.exe knows how to quietly
replace vim-minimal, I'm happy to see Vim in Base.
Yes, truly happy. Gone are
On May 14 01:07, Warren Young wrote:
On 5/13/2013 21:28, Yaakov (Cygwin/X) wrote:
As these utilities are required by
POSIX[1], should the vim-minimal package be added to Base?
As long as when I install vim-kitchensink setup.exe knows how to
quietly replace vim-minimal, I'm happy to see Vim
2013/5/14 Warren Young wrote:
On 5/13/2013 21:28, Yaakov (Cygwin/X) wrote:
As these utilities are required by
POSIX[1], should the vim-minimal package be added to Base?
As long as when I install vim-kitchensink setup.exe knows how to quietly
replace vim-minimal, I'm happy to see Vim in Base.
On 2013-05-14 02:59, Corinna Vinschen wrote:
What bugs me with vim-minimal on Fedora is usually that it's lacking
basic vim functionality, even if it does not rely on external packages.
I'm not quite sure if I remember correctly, but in the past I think I
even had problems with color settings
2013/5/14 Yaakov (Cygwin/X):
Apart from that, yes, vim-minimal should be a Base package, finally ;)
Done.
It overrides the symlink from vi to vim.exe and so this breaks my
current setup:
$ vi
Error detected while processing /home/Frank/.vimrc:
line1:
E319: Sorry, the command is not
2013/5/14 Frank Fesevur:
It overrides the symlink from vi to vim.exe and so this breaks my
current setup:
$ vi
Error detected while processing /home/Frank/.vimrc:
line1:
E319: Sorry, the command is not available in this version: syntax on
Press ENTER or type command to continue
On May 14 04:35, Yaakov (Cygwin/X) wrote:
On 2013-05-14 02:59, Corinna Vinschen wrote:
What bugs me with vim-minimal on Fedora is usually that it's lacking
basic vim functionality, even if it does not rely on external packages.
I'm not quite sure if I remember correctly, but in the past I
On 5/14/2013 04:19, Frank Fesevur wrote:
Any thought other then fixing the symlink manually?
I fixed it with alias vi=vim in my .bashrc.
I've had to do that on assorted Linuxes before, too.
As announced moments ago, I just moved ex/vi into a vim-minimal package,
compiled with the 'small' feature set and not dependent
on vim-common (hence nor perl). As these utilities are required by
POSIX[1], should the vim-minimal package be added to Base?
Yaakov
[1]
On Mon, May 13, 2013 at 10:28:32PM -0500, Yaakov (Cygwin/X) wrote:
As announced moments ago, I just moved ex/vi into a vim-minimal package,
compiled with the 'small' feature set and not dependent
on vim-common (hence nor perl). As these utilities are required by
POSIX[1], should the vim-minimal
13 matches
Mail list logo
