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 crash backtrace. Date: Wed, 09 Nov 2022 14:43:41 +0200 Message-ID: <835yfouwle.fsf@gnu.org> References: <878rkmyoe8.fsf@laptop.lockywolf.net> <87edud7hxj.fsf@yahoo.com> <871qqd7eaw.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9536"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, luangruo@yahoo.com, lockywolf@gmail.com, emacs-devel@gnu.org To: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 09 13:44:12 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 1oskRA-0002Gf-FV for ged-emacs-devel@m.gmane-mx.org; Wed, 09 Nov 2022 13:44:12 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oskQp-0005V3-4y; Wed, 09 Nov 2022 07:43:51 -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 1oskQi-0005TB-Bb for emacs-devel@gnu.org; Wed, 09 Nov 2022 07:43:45 -0500 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 ) id 1oskQh-0006Mi-Tm; Wed, 09 Nov 2022 07:43:43 -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=Rwa2GO+3LYtxwdiFVkR4kBFaX4wMeqB65nNkXW1l/0o=; b=RdIeVAlxbe1U 0OmJqLMNWMECpLMk3lR8eU+csfhbxnjWvm6QoUE8V6z5VHqz4hX0Vjv4BTgE2R3EuDnWr1FzPJNw0 cdYTbU5SsHG1PL/Ygydk4LLQz/RMUwWoUTkYA36vypjl3gyJgjy/uzQTqV/Qzzg5XY4G1QCx+zM47 TYdz199VovD1fKa5ku3YJpaXFzw4DIW0K2ATn55AwG778KxOEdvyusX87klERbynUJPhpkSJNMt7U OA264hUvI2QHWHpxYYVRpHt+qIlOVCMd9D96sxwv1U2oRlo6NH35fUymxgvhUsocQicTATboVm9vb M+tLgvjsjmMAUVWQCOXJCw==; 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 ) id 1oskQh-0005AO-6t; Wed, 09 Nov 2022 07:43:43 -0500 In-Reply-To: (message from Andrea Corallo on Wed, 09 Nov 2022 09:13:13 +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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:299407 Archived-At: > From: Andrea Corallo > Cc: Po Lu , Vladimir Nikishkin , > emacs-devel@gnu.org > Date: Wed, 09 Nov 2022 09:13:13 +0000 > > 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. Why not simply refuse to start in that case? We could add a special command-line option to override that, to leave users a "fire escape".