X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=nRRkAqPAn+e1gZ3s6q1BGn5whQMwwLvK1cGISLRibWeHXOKoPCNta
	AWDv9mzgYW6k8RuwBUmyn2IHyidZUpG+7srGuGFRiRBhfr86yxIUa8EHbHhAfVSb
	SDFac/uodyt2hJBGrbqNlcF3XwzpshRgrPju5CcanlXSk9aClvB8Zk=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; s=default;
	bh=6jQqyqGsubX/eVB8kThl4N1ea9Q=; b=EMbPE2Jd1DdOof/USMTT3o2revtp
	jgsclOR2ns/XDlX7Ho6riPhCe8Ovw8QtvGm5jA3stbZ+1Gi0cVckMvp/i0xmYgGH
	VK1wo2Ly/mCpDx66FtZRlEWDawIgynibiRgu7I2jLy1rHcxNE2NtZZJi2qeh1JRi
	rFxkC2/d0JD9wd0=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-3.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	plane.gmane.org
To:	cygwin AT cygwin DOT com
From:	"Paul.Domaskis" <Paul DOT Domaskis AT gmail DOT com>
Subject:	Re: vi editing at bash command line: cc command doesn't work
Date:	Mon, 8 Sep 2014 23:14:26 +0000 (UTC)
Lines:	36
Message-ID:	<loom.20140909T011053-275@post.gmane.org>
References:	<loom DOT 20140909T004817-488 AT post DOT gmane DOT org>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes

<Paul.Domaskis> writes:
> I needed cygwin on a new work computer that was locked down.  I
> created a DVD from all the 64-bit packages some time in the first
> quarter of 2014, then took the several months needed to get approval
> for its installation.  I then replicated the environment from an old
> work computer with a 32-bit installation of cygwin, including:
>    ~/.inputrc
>    ~/.minttyrc
>    ~/.bash_profile
>    ~/.bashrc
>    /usr/share/vim/vimrc
>    /usr/share/vim/vimfiles
> 
> Everything works well *except* for the fact that when using vi-like
> editing at the bash command line, the cc command does not clear the
> line and enter insert mode.  This is the same regardless of whether
> I am using a mintty or an xterm in X-windows.  However, if I invoke
> vim from either of those 2 environments, cc does work.  It also
> works when I run gvim from xterm, and when I run gvim compiled for
> Microsoft Windows.
> 
> What more can I check to try and narrow down the cause of the
> problem?
> 
> Below, I have pasted in anonymized content from the above files.

<...snip...>

Please note that when I say cc doesn't work with vi-editing at the
bash command line, I mean that nothing happens.

Also, I did not clean up the vimrc file because I suspect that there
is very little chance that it was the culprit.  I believed that
nothing from vimrc is used for vi-editing at the command line.  I
confirmed this just now by renaming /usr/share/vim/vim{rc,files} and
observing the same problem with vi-editing at the command line.


--
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

- Raw text -