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: <20011108115242.71082.qmail@web10903.mail.yahoo.com>
Date: Thu, 8 Nov 2001 11:52:42 +0000 (GMT)
From: =?iso-8859-1?q?Andrew=20McRae?= <andrewmcrae AT yahoo DOT com>
Reply-To: anm AT pobox DOT com
Subject: RE: 1.3.4: rxvt causes tcsh to exit when resized (nt)
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

> Any attempt to resize the rxvt window while at the tcsh prompt will
> cause the window to disappear.

When an rxvt window is resized, the process running in it receives a
SIGWINCH. (This is reasonable; it's what SIGWINCH is for.)

Sending SIGWINCH to a running tcsh process causes it to exit. This
would seem to be the problem.

You can see the signal by setting up a signal handler. For example,
in bash, "kill -l" reports that SIGWINCH is signal 28, so:

    trap "echo caught SIGWINCH" 28

(And of course, you send SIGWINCH to a running tcsh process with
"kill -WINCH <process id>".)

I would think, just off the top of my head, that the fact that
SIGWINCH causes tcsh to exit is a bug.

Regards,
Andrew.

Brandon Phillips wrote:
> Cygwin 1.3.4-4 under Windows XP. rxvt 2.7.2-6, tcsh 6.10.00-3.
> Default shell set to tcsh in /etc/passwd. rxvt invoked via a batch
> file calling "bash --login -i -c rxvt".

> Any attempt to resize the rxvt window while at the tcsh prompt will
> cause the window to disappear. Starting bash, running another copy
> of tcsh and then attempting to resize reveals that it is causing
> tcsh to exit gracefully (the text "exit" is printed as if it had
> been entered as a command). Perhaps tcsh is incorrectly
interpreting
> some terminal control code?

> The following message board article talks about a problem that
> sounds similar. (Hopefully tcsh isn't so neglected that such
> problems are ignored for this long...):
> http://sources.redhat.com/ml/cygwin/2000-06/msg00673.html



=====
Andrew McRae  <anm AT pobox DOT com>

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/