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.help Subject: Re: Is it ok to sort a list of overlays destructively? Date: Thu, 29 Jul 2021 19:53:13 +0300 Message-ID: <83eebhrrie.fsf@gnu.org> References: <87h7ggcov1.fsf@mbork.pl> <83bl6nvpcl.fsf@gnu.org> <87czr3ecpc.fsf@mbork.pl> <83wnpbtbsk.fsf@gnu.org> <87bl6ndlb3.fsf@mbork.pl> <83sfzyu0he.fsf@gnu.org> <83mtq5s3jg.fsf@gnu.org> <83im0trvbq.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22389"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jul 29 18:53:54 2021 Return-path: Envelope-to: geh-help-gnu-emacs@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 1m99IA-0005aX-1W for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 29 Jul 2021 18:53:54 +0200 Original-Received: from localhost ([::1]:51340 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m99I7-00069l-UZ for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 29 Jul 2021 12:53:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39860) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m99Hq-00069M-6V for help-gnu-emacs@gnu.org; Thu, 29 Jul 2021 12:53:34 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:42042) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m99Hp-0007WE-VZ for help-gnu-emacs@gnu.org; Thu, 29 Jul 2021 12:53:33 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2664 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 1m99Hp-0001Yu-Fy for help-gnu-emacs@gnu.org; Thu, 29 Jul 2021 12:53:33 -0400 In-Reply-To: (2QdxY4RzWzUUiLuE@potatochowder.com) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:132183 Archived-At: > Date: Thu, 29 Jul 2021 09:20:21 -0700 > From: 2QdxY4RzWzUUiLuE@potatochowder.com > > > Because anything else is a bug, for the same reason that you > > rightfully expect Emacs not to crash when some Lisp program does > > something silly. > > That's very thought provoking. Thank you. > > If I believe (and maybe I'm old!) that "Emacs is the extensible, > customizable, self-documenting, real-time display editor," then I > wouldn't be surprised at all if some Lisp program caused Emacs to crash. > After all, those Lisp programs have [a great deal of] access to Emacs' > internals. Access to the internals is protected by validity checks that signal Lisp-level errors instead of letting Emacs crash. Emacs crashing is a bad problem because you lose your editing session, so Emacs strives to avoid crashing. About the only thing I know of that a Lisp program can do to crash Emacs is to trigger infinite recursion, and even that has protection in Emacs, albeit not 100% reliable.