Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <5.1.0.14.2.20010618075213.02824008@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 18 Jun 2001 08:02:10 -0700
To: Olaf Foellinger <Olaf DOT Foellinger AT bln DOT sesa DOT de>, cygwin AT cygwin DOT com
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: Re: Latest vim not working with latest mutt
In-Reply-To: <20010618070507.C528@NBOF>
References: <20010615130209 DOT A15896 AT redhat DOT com>
 <3B2A290D DOT 4090903 AT bln DOT sesa DOT de>
 <20010615112907 DOT G15179 AT redhat DOT com>
 <20010615165836 DOT A388 AT NBOF>
 <20010615130209 DOT A15896 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id PAA08804

Olaf,

My any chance are you using rxvt instead of a "stock" console window?

I have noticed that if I close an rxvt window (one that's running BASH) by 
using ALT-F4 or by clicking the close box, the bash.exe process does not 
exit. The next time I log off or shut down, I get the dialog from the 
system complaining that bash.exe won't quit.

By the way, I still see the momentary flash of a Windows console window 
when rxvt starts up.

In contrast, using a Windows console-hosted BASH shell, ALT-F4 is 
inneffective while clicking the window's close box _does_ lead to bash.exe 
exiting. However, unless I shut the shell down via the "exit" or "logout" 
built-ins, the history from that session does not get written, so I imagine 
that clicking the close box (in the console window-hosted BASH) leads to an 
abortive termination, not a "graceful" shutdown.

Windows 2000, SP2, all the latest Cygwin software. Rxvt 2.7.2-6.

% uname -a
CYGWIN_NT-5.0 CLEMENS 1.3.2(0.39/3/2) 2001-05-20 23:28 i686 unknown

% set |egrep BASH_VER
BASH_VERSINFO=([0]="2" [1]="05" [2]="0" [3]="6" [4]="release" 
[5]="i686-pc-cygwin")
BASH_VERSION=$'2.05.0(6)-release'

I'll forgo the cygcheck output, unless someone wants it.

Randall Schulz
Mountain View, CA USA


At 00:05 2001-06-18, Olaf Foellinger wrote:
>On Fri, Jun 15, 2001 at 01:02:09PM -0400, Christopher Faylor wrote:
> > On Fri, Jun 15, 2001 at 04:58:36PM +0000, Olaf Foellinger wrote:
> > >
> > >Thanks, that helped. But gzess how many times the snapshots crashed my
> > >system... :(
> >
> > If snapshots are "crashing your system" then there is something wrong
> > with your system.  There is no way that cygwin1.dll should be able
> > to crash a Win2k system.
>
>Generally I agree with you, a simple process shouldn't crash the system.
>But my experiences with cygwn are a bit different. E.g. I start a bash
>from the autstart folder but when I log out from W2K SP1 the system
>hangs with a message that bash refuses to close. And with the earlier
>snapshots from late may I've had a dump when I tried to mail from mutt
>first in bash and then the complete system did hang or was so slow that
>I did a hard reset. With a later snapshot from June it works now more or
>less (this morning there was a small problem with saving the incoming
>mailbox).
>
>Gruss Olaf
>
>--
>Olaf Föllinger


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple