X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=T4tGNyb+bNaQydXE1LjdlMFb/l13sZKUSRSzWEeOc5R
	K4NVnZ27u7Gp3lam/C61mazjKxV6I2eiQ904PVweJjnpmIL9SiQSmtcz/7fwCRlo
	BchvNzrL2aQh1yjxeAtA4wkuv9k2Oauq1UDx3OBQrIdZEU0onHmAFaGEdjlazbgg
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=68xhsvAc4pJ2lx+/OeOx4rKHcOA=; b=ZfnM/f5WZCM9IW7Va
	BWE45pJcwBKgWFxi4feQRIfteUi0WYZc0w7/Q4Ckp8sA4/cTg/khbvootTU7QC8M
	g+AUk2z+sgZvecizDCbqkW7QJydcv1SmODuDbe/nfz2RPvgnpoSPhxy5hpO4SDIH
	kFE5yhAhX/8knpyF6hq6yIkDNQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: Ishtar.hs.tlinx.org
Message-ID: <544F74A1.6030405@tlinx.org>
Date: Tue, 28 Oct 2014 03:49:05 -0700
From: Linda Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: mintty: WINCH-signal to child
References: <op DOT xnx12ju9ofd6j1 AT nebbiolo DOT upc DOT de> <20141019084829 DOT GA7649 AT dimstar DOT local DOT net> <op DOT xny2kta5ofd6j1 AT nebbiolo DOT upc DOT de> <5443A959 DOT 4030101 AT towo DOT net>
In-Reply-To: <5443A959.4030101@towo.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Thomas Wolff wrote:
> Am 19.10.2014 12:11, schrieb Helmut Karlowski:
>> Am 19.10.2014, 09:48 Uhr, schrieb Duncan Roe:
>>
>>> bash at least has "shopt -s checkwinsize" to achieve what you want,
>>
>> That would be a workaround for bash. Ideally every process should 
>> forward the WINCH-signal to its parent, or the terminal should walk 
>> through the call-tree. Both not very likely to happen.
>>
>> xterm does the same as mintty BTW.
> There must be something more about it:
> Mined does resend a received SIGWINCH to its parent (as an application 
> should indeed) and it's actually received by bash as can be confirmed 
> with 'trap "echo WINCH" SIGWINCH'. Despite of the received signal bash 
> does not adapt its command line width assumption (as can be checked by 
> typing a long line and seeing where it wraps) (unless that option is 
> enabled).
> Probably a bash bug.
> Same in mintty as in xterm in all cases.
> Same on Linux (bash 3.2.39 on Debian on PowerPC), so not cygwin-specific.
----
Do you guys also know there was a change between 4.2 and 4.3 in bash's 
signal handling?  In 4.2, bash used to do child processing inside the 
parent interrupt
which caused problems.  In 4.3, bash waits until a key is pressed before
propagating any signals.

This may be unrelated to whatever problem you are experiencing, but I 
thought
I'd mention you might goog the bash archives on sigwinch and/or winch... 
(not
sure what would be the exact right invocation, but it may not be related
to what you are experiencing anyway...


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