From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: [External] : emacs-28 windows binaries available from alpha Date: Fri, 11 Feb 2022 14:18:45 +0000 Message-ID: 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> <83sfspsks2.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24115"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: dieter@duenenhof-wilhelm.de, corwin@bru.st, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Feb 11 15:24:40 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 1nIWqm-00067F-5z for ged-emacs-devel@m.gmane-mx.org; Fri, 11 Feb 2022 15:24:40 +0100 Original-Received: from localhost ([::1]:38336 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nIWqk-0006hJ-TQ for ged-emacs-devel@m.gmane-mx.org; Fri, 11 Feb 2022 09:24:38 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:42490) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nIWlF-0000dd-Vq for emacs-devel@gnu.org; Fri, 11 Feb 2022 09:18:58 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:56913) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nIWlE-000398-5y; Fri, 11 Feb 2022 09:18:57 -0500 Original-Received: from ma.sdf.org (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 21BEIjK3008372 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Fri, 11 Feb 2022 14:18:45 GMT In-Reply-To: <83sfspsks2.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Feb 2022 13:30:21 +0200") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:286166 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: dieter@duenenhof-wilhelm.de, corwin@bru.st, emacs-devel@gnu.org >> Date: Fri, 11 Feb 2022 09:16:25 +0000 >> >> >> 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. > > This is unlikely to happen if the user has libgccjit installed: if it > is found when building Emacs, it will most probably be also found when > running it. Because is unlikely is suspect might be of interest in this case. > So the warning will mostly show when the user installed Emacs built by > someone else. In which case, the user already made the decision not > to install libgccjit, so warning the user about that would be in > many/most cases redundant. How do we know the user made this decision intentionally? Best Regards Andrea