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: Emacs crash backtrace. Date: Wed, 09 Nov 2022 15:17:32 +0000 Message-ID: References: <878rkmyoe8.fsf@laptop.lockywolf.net> <87edud7hxj.fsf@yahoo.com> <871qqd7eaw.fsf@yahoo.com> <87fses5ldo.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9926"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Stefan Monnier , Vladimir Nikishkin , emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 09 16:18: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 1osmq4-0002S1-DJ for ged-emacs-devel@m.gmane-mx.org; Wed, 09 Nov 2022 16:18:04 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1osmpf-0001so-7j; Wed, 09 Nov 2022 10:17:39 -0500 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 ) id 1osmpc-0001dH-VE for emacs-devel@gnu.org; Wed, 09 Nov 2022 10:17:37 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1osmpb-00031a-EZ for emacs-devel@gnu.org; Wed, 09 Nov 2022 10:17:36 -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 2A9FHWIJ014559 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Wed, 9 Nov 2022 15:17:32 GMT In-Reply-To: <87fses5ldo.fsf@yahoo.com> (Po Lu's message of "Wed, 09 Nov 2022 21:05:07 +0800") 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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:299412 Archived-At: Po Lu writes: > Andrea Corallo writes: > >> Stefan Monnier writes: >> >>> Po Lu [2022-11-08 21:42:47] wrote: >>>> Andrea Corallo writes: >>>>> not sure if this was discussed already but, shouldn't we warn the user >>>>> running an Emacs in such unsupported configuration? >>>> That's already done so, in NEWS and other associated documentation. >>> >>> I think Andrea was thinking of something more "in your face", like on >>> the splash screen or in the *scratch* buffer's initial text, or as >>> a `display-warning`, ... >> >> Exactly, if Emacs is not supposed to work properly in a certain >> configuration I believe we definitely should inform the user of this. >> >> Andrea > > Sounds reasonable, now done. Thanks Po Lu Andrea