From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: emacs-repository-{version|branch} on Windows
Date: Sat, 05 Nov 2022 08:24:57 +0200
Message-ID: <83pme1535y.fsf@gnu.org>
References: <CAAeL0SRxiByrjFrwKi+-EzTvAAbd0Ugvp-xmXkyLy1=s-ak1XA@mail.gmail.com>
 <83v8nu4kp6.fsf@gnu.org> <jwviljuv7wj.fsf-monnier+emacs@gnu.org>
 <CAAeL0SQxzOqCT0xyzR04N1GYvrb+1v_TjnisODnG+SeCGj3vWQ@mail.gmail.com>
 <83tu3e4g5n.fsf@gnu.org>
 <CAAeL0SR7c3HfuJ_b+=dXvsoAwRUNXH8aGpnzPCL8yxL=3oA5=Q@mail.gmail.com>
 <jwvk04atpky.fsf-monnier+emacs@gnu.org> <83r0yi4exj.fsf@gnu.org>
 <jwv8rkqto3t.fsf-monnier+emacs@gnu.org>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="35443"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: lekktu@gmail.com, emacs-devel@gnu.org
To: Stefan Monnier <monnier@iro.umontreal.ca>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 05 07:26:11 2022
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1orCd8-00093M-5T
	for ged-emacs-devel@m.gmane-mx.org; Sat, 05 Nov 2022 07:26:10 +0100
Original-Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces@gnu.org>)
	id 1orCcC-0004rB-40; Sat, 05 Nov 2022 02:25:12 -0400
Original-Received: from eggs.gnu.org ([2001:470:142:3::10])
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>) id 1orCc7-0004qb-4b
 for emacs-devel@gnu.org; Sat, 05 Nov 2022 02:25:10 -0400
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1orCc3-0002Ac-Vz; Sat, 05 Nov 2022 02:25:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
 mime-version; bh=jVNgF3x7Q3E1H6nLuyw7MGP93me+m+WmJgpp4iCpYbM=; b=mZyDH6wqqaNK
 +AclI0xM7P1E9r/3XbshUUNgi5bvQz4r62yOUqwtU7oDjXM/Xx8JB6cXnevqkS9UiK1p/kAEMLBMT
 3wkYv4KDUwVyC4qxAn3NAqZbbI/WUtzuePjYjKnIB1vLryqHhg9WAPeo1Qlz7x8tg4gjdyrxMwWRS
 ze5OwaRWHCq2+C+Ro4R5+dZ6IA3wTwag4/1+qBGCwVDVYPQq6RlpPu8Hgi6nqIB9e0YAwcx7KBJKf
 nwHd/rxFQb6WXXQ3fPUs46PoQ/lB+bTJ/bJxD3+aKK9qIRibrYWoffQgLc5X/QQ7/96kTeKrwy0Yc
 UaATK4DvEGwSqs15d4eSug==;
Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1orCc3-0000BP-3d; Sat, 05 Nov 2022 02:25:03 -0400
In-Reply-To: <jwv8rkqto3t.fsf-monnier+emacs@gnu.org> (message from Stefan
 Monnier on Fri, 04 Nov 2022 17:20:31 -0400)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Original-Sender: "Emacs-devel" <emacs-devel-bounces@gnu.org>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Xref: news.gmane.io gmane.emacs.devel:299171
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/299171>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: lekktu@gmail.com,  emacs-devel@gnu.org
> Date: Fri, 04 Nov 2022 17:20:31 -0400
> 
> >> Maybe the better way forward is to tweak the code so it doesn't silence
> >> this kind of error.
> > Then you'd hit a much worse extremity: that the user is annoyed by
> > problems most of them don't understand and don't want to know about.
> 
> Not necessarily, depends when/where we show the error.  AFAIK this code
> is run while building Emacs, so emitting an error during compilation
> wouldn't be too intrusive (as long as it doesn't prevent the build from
> succeeding).
> Or we could put the error message into those vars.

Those errors show in each and every file-related operation.