X-Recipient: archive-cygwin@delorie.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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=BfFdwSWeEqAe0bwL
	MV9mkT6y+p1jqFgfSFhL/pF0zWDk1Htkj0DNLUSMibspbdV2vzJWZO7IDDqS9FSL
	Ztp0u6E8DlO/Lx7fmtVdvK62DGZPXWA7g7kqtTKxoBLiMbnzuyqh2XY8WF575MoU
	R2al8Z0cMlxPmvOG0fomXnNJEpE=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=UqSVRqzQ6THs1rfHDSby8V
	iRE4Y=; b=IMYaGbfg6WvE5fyjpwMd5nTJQa/FE1bEU3+s/CnaKKMwEkKLF8lR5Y
	lcuTRsqhdftQfVPZVRdVyT6tx5+6Yfv3qDJj0ypz9/jJf5qk/bz/0uInh24LeUj9
	pI7bXIzG6GmDql6N6bgeFjnRH6brI/jUU2dXfVxlKLE2ES/SIJ5ow=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=pulled, H*f:sk:1610701, H*i:sk:1610701, H*MI:sk:1610701
X-HELO: smtp-out-so.shaw.ca
Reply-To: Brian.Inglis@SystematicSw.ab.ca
Subject: Re: cygwin 3.1 pseudo console in PTY and break/ctrl-c handling
To: cygwin@cygwin.com
References: <937489593.4978154.1582060605719.ref@mail.yahoo.com> <937489593.4978154.1582060605719@mail.yahoo.com> <b579ee20-ff91-b633-594f-d7dee81936f8@towo.net> <1610701589.5557144.1582142570779@mail.yahoo.com>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Message-ID: <a10b0144-34b0-5ea7-31f7-acd5c94f275a@SystematicSw.ab.ca>
Date: Wed, 19 Feb 2020 13:21:36 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version: 1.0
In-Reply-To: <1610701589.5557144.1582142570779@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes

On 2020-02-19 13:02, Kevin Schnitzius via cygwin wrote:
> On Tuesday, February 18, 2020, 05:54:23 PM EST, Thomas Wolff wrote: 
>>> With 3.1.2-1:
>>> mintty -o "CA+F12:break"               =====>    ctrl-alt-F12 causes a break and kills notepad
>>> mintty -o "c:break"                    =====>    ctrl-shift-c causes a break and kills notepad
>>> mintty -o "C+c:break"                  =====>  FAIL -- ctrl-c kills native apps but notepad is not affected
>>> mintty -o "CA+c:break"                 =====>  FAIL -- ctrl-alt-c kills native apps but notepad is not affected
>>
>> This would be mintty -o KeyFunctions='CA+F12:break' etc.
>> The latter two are not valid mintty configuration; Ctrl is only 
>> supported as a modifier for function keys and special keys, not letters. 
>> This is unchanged with the cygwin version.
> 
> Ah, thank you.  That was the clue that I needed.
> 
> For those also having this problem:
> 
> mintty.exe -o "KeyFunctions=c:break" -o CtrlExchangeShift=true -
> 
> will propagate Ctrl-C to the non-native apps and kill them, imitating the behavior of 3.0.X Cygwin.
> 
> Now that I have played with this for a while, I am thinking that I like the new behavior better and I have assigned a new key to specifically kill native Windows programs instead letting the Ctrl-C do all the work (I am using Alt-F5 to do this).

Should the above settings not be the default behaviour for backward
compatibility and least surprise to users?

It used to be mintty just worked as expected with most programs, now additional
interfaces seem to be required depending on Windows versions, editions, and
releases. These helpers should either be included in the package, or be
dependencies pulled in by mintty without which it will not install, with the
appropriate interfaces installed and configured so that mintty, shells, and
programs run under it continue to work as expected.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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

