DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=Ygg
	c3V7ztZQwel0FHtd15ceCDArF7fPaMJBExBzQ22QgLiOuLIHzMIOxPwmijNzeoxi
	KZJtSXRomfo4Md0GM9j5ZJ6u1zchBNbVz9Pq5MEsU1l+BEmxBNuGRCaI7YTUznD0
	ciMftBlmb1JPKTUGbSU1QxF6eR5BAQ4hOD/9JeuM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Shaun Fielder" <kveldulv@outbacktrip.info>
To: <cygwin@cygwin.com>
Subject: vim-minimal annoyance
Date: Mon, 17 Jun 2013 12:54:13 +1000
Message-ID: <002d01ce6b05$f2f16d40$d8d447c0$@outbacktrip.info>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Since the vim-minimal package came into existence, it's caused a fair bit of
mucking around and frustration here (broken .vimrc; time to figure out
what's going on). (Especially as each update wants to re-install vim-minimal
which we don't want.)

We're so used to vi === vim [fully featured] on Cygwin. At the very least -
when the full "vim" package is installed 'vi' should use it.
At the moment, I'm having to get everyone here to uninstall vim-minimal and
manually setup a sym-link (or alias) to get back to the behaviour they've
always had.

Shaun


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple