From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs 27.1 Windows Binaries -- testing wanted Date: Mon, 24 Aug 2020 20:10:17 +0300 Message-ID: <83tuws55s6.fsf@gnu.org> References: <83pn7oft7r.fsf@gnu.org> <5fd1bc533b4bfe603d106fb3ee816208@russet.org.uk> <83364keznu.fsf@gnu.org> <87imdgrlpq.fsf@telefonica.net> <83tuwzewxa.fsf@gnu.org> <87eeo3sxw0.fsf@telefonica.net> <47436f6137c965db141e290de6597fd5@russet.org.uk> <464a5bf221d1d77ea13381fb901931fd@russet.org.uk> <834kovbx7x.fsf@gnu.org> <83a6yk72ec.fsf@gnu.org> <83wo1o59kt.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39212"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rpluim@gmail.com, phillip.lord@russet.org.uk, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 24 19:11:06 2020 Return-path: 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 ) id 1kAFzu-000A6i-GE for ged-emacs-devel@m.gmane-mx.org; Mon, 24 Aug 2020 19:11:06 +0200 Original-Received: from localhost ([::1]:45376 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kAFzt-0007zB-IA for ged-emacs-devel@m.gmane-mx.org; Mon, 24 Aug 2020 13:11:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38300) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kAFzN-0007YY-66 for emacs-devel@gnu.org; Mon, 24 Aug 2020 13:10:33 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49558) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kAFzM-0004Tb-8o; Mon, 24 Aug 2020 13:10:32 -0400 Original-Received: from [176.228.60.248] (port=2944 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kAFzL-0004pC-IR; Mon, 24 Aug 2020 13:10:31 -0400 In-Reply-To: (message from Stefan Monnier on Mon, 24 Aug 2020 12:49:26 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:254194 Archived-At: > From: Stefan Monnier > Cc: rpluim@gmail.com, emacs-devel@gnu.org, phillip.lord@russet.org.uk > Date: Mon, 24 Aug 2020 12:49:26 -0400 > > For me, the purpose of such a list of features is to help the user > figure out whether a given problem comes from their config or from the > Emacs build itself. I don't see how this can be done in principle. There are too many factors that affect the final outcome, and telling which ones are due to the build and which are due to the run-time environment not directly related to the build, is night impossible, certainly by running a few naïve tests. I believe that you are still thinking about Posix platforms, where any feature compiled in should be automatically available, but this thread is not about a general-purpose facility, it's about w32-specific facility, where things are more complex.