X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 51C303857C73
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1706879239;
	bh=E5SGU1x5xqkYtcQnQuZotcw/MyGWWJKeyCxBNgBiasU=;
	h=Date:Subject:References:Cc:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=H5TBADjmrYI3HnooAQHXXOHCTwT4sgMTBewMttTR6xvdCQsIZHiBsZ+FNdf3uXETz
	LXKsGZqrkRVLVf4hahhptKmERb3NVgoKnFdzd8qTY9hT837fMICkG9PYVs8rDBF/lb
	ohkJmsGnWnSHylQ4d8nHRryjJlhwpE9PWOQfr7gI=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 718A53858403
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org 718A53858403
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1706879213; cv=none;
	b=UUVtY6aFFGvgiQb3YR656KNaWIIJwr7r4vkxTRMxvf5KN6mU4DYks0lL6WGn36isv9ZTORPQCnnS5NHP/t8X7QBUXdLp7N4FF6KODrcnDkVtFPaS36Tj+tgmsSHl/YA+Sa6ryQFoePLy45Id7iKgghImLdqzX80hAo5rwpyp7wc=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1706879213; c=relaxed/simple;
	bh=mSuXGuKeFio48S822b8ZyZurVKUqmxZSthR1FE8zSHk=;
	h=Message-ID:Date:MIME-Version:Subject:From;
	b=pUm9r5ZrsuRZwEwk9E28ayWkbL8jfKGNgG0FQAl7Tfw9aNUXtcwPy+gmkBgNcKtMztwJbPvX4Vj+E+vxEQzZXOtbEE1QhuG0G9i4aP2JeN6zqKof0mgK5kh8gca2+jNXQREEkKxm0WahaPNI8WlYo3ftGeQ+4cAPjw0QNZ+wg+s=
ARC-Authentication-Results:	i=1; server2.sourceware.org
X-SNCR-Rigid:	65A5686F02769CED
X-Originating-IP:	[86.140.193.68]
X-OWM-Source-IP:	86.140.193.68
X-OWM-Env-Sender:	jon DOT turney AT dronecode DOT org DOT uk
X-VadeSecure-score:	verdict=clean score=30/300, class=clean
X-RazorGate-Vade:	gggruggvucftvghtrhhoucdtuddrgedvkedrfedugedggeejucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecumhhishhsihhnghcuvffquchfihgvlhguucdlfedtmdenucfjughrpefkffggfgfufhfhvegjtgfgsehtjeertddtvdejnecuhfhrohhmpeflohhnucfvuhhrnhgvhicuoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqeenucggtffrrghtthgvrhhnpefhueejheefuddvfeekhfevffffvefhgeetuddtieekkeffgeegleejleeugedvteenucffohhmrghinheptgihghifihhnrdgtohhmpdhgihhthhhusgdrtghomhenucfkphepkeeirddugedtrdduleefrdeikeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddruddtlegnpdhinhgvthepkeeirddugedtrdduleefrdeikedpmhgrihhlfhhrohhmpehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkpdhnsggprhgtphhtthhopedupdhrtghpthhtoheptgihghifihhnsegthihgfihinhdrtghomhdprhgvvhfkrfephhhoshhtkeeiqddugedtqdduleefqdeikedrrhgrnhhgvgekiedqudegtddrsghttggvnhhtrhgrlhhplhhushdrtghomhdprghuthhhpghushgvrhepjhhonhhtuhhrnhgvhiessghtihhnthgvrhhnvghtrdgtohhm
	pdhgvghokffrpefiuedpoffvtefjohhsthepshgrqdhprhguqdhrghhouhhtqddttdeh
X-RazorGate-Vade-Verdict:	clean 30
X-RazorGate-Vade-Classification:	clean
Message-ID:	<16b354c2-bba4-40b8-8359-7eb9a79b3ee3@dronecode.org.uk>
Date:	Fri, 2 Feb 2024 13:06:47 +0000
MIME-Version:	1.0
User-Agent:	Mozilla Thunderbird
Subject:	Re: Restore SEM_FAILCRITICALERRORS [was: Aren't Windows System Error
	popups meant to be disabled in Cygwin?]
References:	<CAJQQdJiOEduFeAthZ+q+LNXV33aJOhAXqq3sCaxdCqRpAjVmvA AT mail DOT gmail DOT com>
	<CAB8Xom-PnumWSLoDFgERXA4GX0zotQiKFvi_wL7Bvsv133WAmw AT mail DOT gmail DOT com>
	<CAJQQdJhzSNZ5dG254g5dv_AuWRxt+R-HLdiCPTkCNv=o+4PVeQ AT mail DOT gmail DOT com>
	<ZbtsBD2IKYtH-duQ AT calimero DOT vinschen DOT de>
	<CAJQQdJhS3QgJe_KsfGof_6XM6cwtNRkbPQPR32-JaKCu8_8KEA AT mail DOT gmail DOT com>
	<ZbzmLRByzmDJxUcb AT calimero DOT vinschen DOT de>
Cc:	cygwin AT cygwin DOT com
In-Reply-To:	<ZbzmLRByzmDJxUcb@calimero.vinschen.de>
X-Spam-Status:	No, score=-1.5 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
	KAM_DMARC_STATUS, MISSING_HEADERS, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS, SPF_PASS,
	TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version:	SpamAssassin 3.4.6 (2021-04-09) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Jon Turney via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On 02/02/2024 12:55, Corinna Vinschen via Cygwin wrote:
> On Feb  2 09:43, David Allsopp via Cygwin wrote:
>> On Thu, 1 Feb 2024 at 10:02, Corinna Vinschen via Cygwin
>> <cygwin AT cygwin DOT com> wrote:
>>>
>>> The behaviour changed in 2020
>>>
>>> https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=21ec498d7f912
>>>
>>> not without a discussion
>>>
>>> https://cygwin.com/pipermail/cygwin-patches/2020q4/010870.html
>>
>> Aha, thank you! (congrats on the 3.5 release, in passing, btw).
>> Definitely not a regression, then (subject edited).
>>
>> However, this patch came from MSYS2, and subsequently they seem to
>> have found it problematic for the same reason as me
>> (https://github.com/msys2/msys2-runtime/pull/18#issuecomment-810897624)
>> and have just recently reintroduced the flag
>> (https://github.com/msys2/msys2-runtime/commit/7616b8a2e0ffcf068b47e1a66bbb1dbd7d9b5c50)
>> to control it.
>>
>> The reasoning in
>> https://cygwin.com/pipermail/cygwin/2006-August/150081.html seems as
>> valid now as it did in 2006.
>>
>> Is it possible to revisit having the flag, or even just reverting the behaviour?
>>
>> FWIW, it's been "hurting" us over in OCaml-land since zstd support was
>> added roughly a year ago - configure can tell us that mingw-w64's zstd
>> is available, but woe betide us if we run the test program to see if
>> it actually works, but the user forgot to add the sys-root into PATH,
>> because at that point the CI system is down...
> 
> I'm sympathetic, and personally I would prefer to revert the patch and
> stick to SEM_FAILCRITICALERRORS by default.
> 
> The question is this: Why does, apparently, everybody expect Cygwin to
> do the "right thing", with different definitions of "right", when in
> fact the executable in question can easily call SetErrorMode by itself?

Yeah, if cygwin wasn't involved in the process ancestry, how would you 
get the behaviour you want?

I guess perhaps what's needed here is a command-wrapper tool like 'nice' 
or 'env' which lets you run a command with the error-handling mode you want.

But that must already exist for Windows, right? :)


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

- Raw text -