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:from:to:date:subject:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=HSCMwfLE9LW+QLo9662GC6bXYE3A5
	gCKQsUkj6KFLjwWi8yo6IJfA/LZ/Oscxq2DdvpJm4BC/6GCwJSS5dA8ruXwNwfu4
	/YvlytlV49fVMCD62xv0+s4HEjA1q5DNjEkDKbCpLhjR5KqMItCkB9i3Ku4kf6oo
	K1IwOTSG3xQSYo=
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:from:to:date:subject:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=hKuW4RuwdjuIQB++MI/IKkqon8k=; b=mXB
	XQHULC0Fdi8vBHGeMNgDlZQfkn8F2609UZAy2k9Geo0MKxes2qgSQ6fb/8dd9Wkz
	23aexGZsixpDzFsgIb9D4uuQV/Yweog0jsOup1sBGH6kLQ8WfWcFyWTMwArqkV+X
	+vqFFdkJP126y5Mp6GxO/4w+XsmqczrJl6GA/RSk=
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=-1.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	ecl1mtaoutpex02.symantec.com
From:	Bob McGowan <Bob_McGowan AT symantec DOT com>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date:	Tue, 9 Sep 2014 09:12:43 -0700
Subject:	Re: vi editing at bash command line: cc command doesn't work
Message-ID:	<D0346D8C.35C1%bob_mcgowan@symantec.com>
References:	<loom DOT 20140909T004817-488 AT post DOT gmane DOT org> <loom DOT 20140909T011053-275 AT post DOT gmane DOT org> <loom DOT 20140909T155332-684 AT post DOT gmane DOT org>
In-Reply-To:	<loom.20140909T155332-684@post.gmane.org>
user-agent:	Microsoft-MacOutlook/14.4.4.140807
MIME-Version:	1.0
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id s89GDljt032126

I have the same problem.  My system details (abbreviated):

Windows 7 Home Premium Ver 6.1 Build 7601 Service Pack 1


Cygwin installations found in the registry:
  System: Key: e022582115c10879 Path: C:\cygwin64
  User:   Key: e022582115c10879 Path: C:\cygwin64

  Cygwin DLL version info:
      DLL version: 1.7.29

This is a standard installation using Cygwin setup program.


I've just updated to dll version 1.7.32 and the problem persists.

The above was done in an xterm window, but it also happens in the standard
Cygwin64 Terminal started from the desktop shortcut.


I've installed mksh, which also supports vi style command line editing,
and both 'cc' and 'dd' work as expected there.

Bob

On 9/9/14, 7:02 AM, "Paul.Domaskis" <Paul DOT Domaskis AT gmail DOT com> wrote:

><Paul.Domaskis> writes:
>><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?
>
>   <...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.
>
>Just noticing that it also affects the dd command too.  That is,
>nothing happens.
>
>I'm not sure how many people actually use vi key bindings at the bash
>command line.  If you do, and you have none of the above problems with
>the 64-bit install, could you please chime in so that I know that
>there is a solution (even though I may not know what that solution
>is).
>
>Thanks.
>
>
>--
>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
>


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