X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Fri, 11 Dec 2009 10:38:26 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin 1.5.25, vim 7.2-3: Command 'cw' misbehaves on a block  of contiguous white-spaces
Message-ID: <20091211093826.GY8059@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <333442.20990.qm@web53303.mail.re2.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <333442.20990.qm@web53303.mail.re2.yahoo.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Dec 10 19:17, Avijit Ghosh wrote:
> VIM seems to be behaving improperly executing the 'cw' command when the
> cursor is positioned on a block of contiguous white-space characters.
> 
> It is changing *only* the character it is positioned on (instead of changing
> up to the last white-space in the block).
> 
> Consider the following example text (please read using fixed-width font):
> 
> alpha       beta
>      ^
>      Cursor here
> 
> If I type 'cw<ESC>', I get:
> 
> alpha      beta
> 
> I expect, based on using Win32 native VIM 7.2, Cygwin VIM 6.x, and other
> VIM/vi on Unix platforms -- and also on behavior or 'dw' or just 'w' on
> *this* version of VIM:
> 
> alphabeta
> 
> That is, I expect 'cw' to be equivalent in general to 'dwi', and 'cw<ESC>'
> to be equivalent to 'dw' --- this is not the case any more, it seems.

Works exactly as you expect it for me.  I guess you have to blame one of
your vim startup files like ~/.vimrc.


Corinna


-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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