Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Fri, 30 Mar 2001 13:30:03 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Problem: is it Vim or cygwin/bash setting? Message-ID: <20010330133003.Q16622@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.com References: <3AC43945.AAE38BD5@verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AC43945.AAE38BD5@verizon.net>; from rich.coco@verizon.net on Fri, Mar 30, 2001 at 02:44:05AM -0500 On Fri, Mar 30, 2001 at 02:44:05AM -0500, rich coco wrote: > In an older B20 release of cygwin, when i used Vim to edit a file and > eventually exited, my window reverted to the state it was in prior to > the vim session (ie, the text being editied by vim is no longer > visible). > > I upgraded to the latest cygwin release (i was missing groff, > ghostscript, lots more...) and noticed that the above behavior - which i > > prefer - does not occur. That is, when I quit my Vim session, the text I > > was editing stays on my screen, clobbering the pre-vim context. > > i cannot determine if this is a Vim configuration thing or a > shell-configuration thing. > What can I modify - if anything - to get the behavior i want? The cygwin console mode currently doesn't support that. I have just added that to the CVS repository. It will be available in the next version of Cygwin. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple