On Sun, Jun 30, 2013 at 01:37:36AM +0200, Nikola Pavlović wrote: > Hello, > > Is it just me, or did the last revision[*] of editors/vim break options > for both it and editors/vim-lite? When I try to update vim-lite > optional dependencies from vim are forced on this port, so I get > mandatory Python, Lua, Ruby... with vim-lite. :) > > I only ever install vim-lite, so just out of curiosity I tried make > config in vim, and it said there are no options to configure, so > something is definitely wrong with that. > > Yesterday I upgraded vim-lite on the same machine (in a different jail, > and outside) and it worked fine. > > I couldn't spot the error immediately, and I'm not really up to > date with OptionsNG ATM to tinker. > > > [*] http://svnweb.freebsd.org/ports?view=revision&revision=322016 > > > -- > Big M, Little M, many mumbling mice > Are making midnight music in the moonlight, > Mighty nice! > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
I have fixed vim-lite so that its default options are sane again. I still don't get what VIM_OPTIONS brings to the users that the options with the same default didn't bring to them except a dialog4ports window prompting? If the problem is just that this dialog4ports window is bring prompt? One can just set NO_DIALOG=yes in make.conf. Given that VIM_PORT_SCRIPT_LANGS will allow to tune vim the same way options does almost but that will not be consistent with the general way. regards, Bapt
pgpJYjvOmNSo1.pgp
Description: PGP signature
