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: [External] : emacs-28 windows binaries available from alpha Date: Fri, 11 Feb 2022 13:31:00 +0200 Message-ID: <83r189skqz.fsf@gnu.org> References: <834k5d3hbv.fsf@gnu.org> <83o83l1v51.fsf@gnu.org> <83k0e3vox9.fsf@gnu.org> <83fsoruv2u.fsf@gnu.org> <83o83eudgz.fsf@gnu.org> <83ee4atzh5.fsf@gnu.org> <83v8xlst5p.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39000"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dieter@duenenhof-wilhelm.de, corwin@bru.st, emacs-devel@gnu.org To: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Feb 11 12:36:04 2022 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 1nIUDc-0009ub-IL for ged-emacs-devel@m.gmane-mx.org; Fri, 11 Feb 2022 12:36:04 +0100 Original-Received: from localhost ([::1]:37474 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nIUDb-00078L-Gr for ged-emacs-devel@m.gmane-mx.org; Fri, 11 Feb 2022 06:36:03 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58604) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nIU8n-0000FM-3B for emacs-devel@gnu.org; Fri, 11 Feb 2022 06:31:05 -0500 Original-Received: from [2001:470:142:3::e] (port=59748 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nIU8m-0003ZX-Kx; Fri, 11 Feb 2022 06:31:04 -0500 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=w8bnG9KN9dq4cSpQn/OuF2JnnGvPBvdqVDZBAf5aZ9Q=; b=meLr1GJHUEHf YDUKDpjiutB55fy7ufsCCxod1MdSBN+tDT/SISoirSzEwdSjwv9/hirjDWRS8BGPWOurKIynsPBq+ bT2dlBVHCDD6sBuiqFY8rIybrz/XjgqYwx5lpIAN5kbT667AO/puyQ4LJlIrh3V6xViNUxRgsKkcr a4z+kBuuAxi9BOee3LmgTh4DFhmFd1syYCEIUt9ekOepyAd+gLemE9qW3dMbMAxp8ZVFbIjIKKsF1 sS0MNxFDxcvm9rwHG3oOIIYXkk84zPN/J5PFT6iAryK6as4WSXXAAhUCdw4Ajf+RgBSo+hTgd7j5K dpmS+SoPnJ6YY6U2QegY9A==; Original-Received: from [87.69.77.57] (port=2907 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nIU8l-0002sp-UX; Fri, 11 Feb 2022 06:31:04 -0500 In-Reply-To: (message from Andrea Corallo on Fri, 11 Feb 2022 09:21:52 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:286163 Archived-At: > From: Andrea Corallo > Cc: dieter@duenenhof-wilhelm.de, corwin@bru.st, emacs-devel@gnu.org > Date: Fri, 11 Feb 2022 09:21:52 +0000 > > Andrea Corallo writes: > > > Eli Zaretskii writes: > > [...] > > >>> Anyway I was thinking if it wouldn't be correct to emit also a warning > >>> if libgccjit is not available. This condition could prevent some > >>> package to work as expected (ex evil-mode IIRC) so might be worth to > >>> inform the user that and emacs compiled with native-comp is being run > >>> without libgccjit being available. > >> > >> I'm not sure I see the usefulness of such a warning. If Emacs works > >> correctly regardless, the warning could annoy. So I tend to think we > >> should introduce the warning only if enough users complain that Emacs > >> silently does something they'd prefer to know about. > > > > I think it might be useful for two reasons: > > > > 1- let the user know that a native compiled Emacs is being run without > > access to libgccjit, not only it might not function as expected but > > most likely I guess that if the user compiled a native compiled Emacs > > he wants to have it working with native code. So in general I guess > > it might be informative. > > > > 2- help us identifying the issue when a bug is opened because of it, if > > we suspect that's the problem we can ask the user to have a look to > > the warnings. > > > > But indeed I'm not sure it's worth of so I asked. > > > > An alternative to point two would be having a trace of this in M-x > > report-emacs-bug. > > Thinking about I think this might be a good idea anyway. I agree. Would you mind proposing a patch?