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
From: "Jonadab the Unsightly One" <jonadab AT bright DOT net>
Organization: There is no organisation.
To: cygwin AT cygwin DOT com
Date: Wed, 30 May 2001 21:39:31 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Possible bug? Re: Strange behaviour when closing cygwin
Reply-to: jonadab AT bright DOT net
Message-ID: <3B156893.20241.4837FD@localhost>
In-reply-to: <20010530102222.I17603@redhat.com>
X-Eric-Conspiracy: My name is not Eric.
X-Platform: Windows '95 OSR2 (heavily adjusted and customised)
X-Eric-Conspiracy: My name is not Eric.
X-Platform: Windows '95 OSR2 (heavily adjusted and customised)
X-mailer: Pegasus Mail for Win32 (v3.12)


# >>>Once pressed the key sequence seems to get
# >>>stored and is only
# >>
# >>It's a W2K "feature" which is related to starting Cygwin via a batch
# >>file.  You can't change that AFAIK.
# 
# You can generalize Corinna's message from W2K to Windows.  
# It's a Windows feature.

I'm using Cygwin (just got the latest version this week, 
but I had a slightly earlier version since earlier this 
year) on Windows 95 OSR 2 and have never experienced this 
probem at any time.  I can start a bash shell, press 
ctrl-c any number of times I like in whatever circumstances 
I want, and then type logout and the bash window vanishes
forthwith, sans passing go or collecting $200.

I *do* have a problem where if a cygwin window (whether
bash or somethinge else doesn't seem to matter) is in
the _foreground_ while wincron launches another process,
the cygwin window will stop responding.  (Asicutil2 is
what gets blamed as "[Not Responding]" in the Close
Program dialogue box.)  Is this an unrelated problem,
possibly a wincron problem?  It only happens when
cygwin is in the foreground when the new process is
launched; if anything else has the focus it doesn't 
happen.

The nature of the launched process is probably not
important; it's usually a batch file (because that's 
what I usually launch from wincron).  Also, the
launched process generally doesn't *do* anything
except sit in the taskbar until I kill off 
asicutil2, at which point the new launched process
does whatever it was going to do.

-- jonadab

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