Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Mon, 3 Jan 2005 11:02:41 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: vi "W10: Warning: Changing a readonly file" on large read-write file
Message-ID: <20050103100241.GC12820@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <ECEEJLCHJDLKMHGOACFJAEGMCDAA DOT bax3 DOT NO AT SPAM DOT bigfoot DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ECEEJLCHJDLKMHGOACFJAEGMCDAA.bax3.NO@SPAM.bigfoot.com>
User-Agent: Mutt/1.4.2i

On Jan  1 04:52, Michael Bax wrote:
> When attempting to edit a *writeable* file of "zero" lines but 53 MB in size
> (no newlines), vi appears to hang.

But it doesn't.  It just needs a lot of time to process the file.
After all vim is an editor.  It searches the whole file for line-endings
etc.  Try the same on another OS and you'll see the same effect.  On my
Linux box vi needs three or four minutes to scan such a file and to
become responsive again.  It eats up all CPU time while doing that.
Actually vim is not my preferred editor to edit binary files.


Corinna

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

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