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=br7GvfdZZMuPoHz2gUVl3KiUR3z+AYxHi7nzy7OIzfVPwIGMdoj54
	bqdW7ULAna/BQ1MYx5xeedroN/69SFUuviIeyB1Q4OZ0SdE5yAvCw3zQhta8l+Bz
	65DLuxAFtBlUOJZcnDG9VgELrjHQVPrmUyUnTftAjJeFySY0RtS6I4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: "Paul.Domaskis" <Paul.Domaskis@gmail.com>
Subject: Re: vi editing at bash command line: cc command doesn't work
Date: Tue, 9 Sep 2014 14:02:42 +0000 (UTC)
Lines: 47
Message-ID: <loom.20140909T155332-684@post.gmane.org>
References: <loom.20140909T004817-488@post.gmane.org> <loom.20140909T011053-275@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)

<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