all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Is it ok to sort a list of overlays destructively?
Date: Thu, 29 Jul 2021 19:53:13 +0300	[thread overview]
Message-ID: <83eebhrrie.fsf@gnu.org> (raw)
In-Reply-To: <YQLVRZrk8bcrQpDt@scrozzle> (2QdxY4RzWzUUiLuE@potatochowder.com)

> 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.



  reply	other threads:[~2021-07-29 16:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  5:22 Is it ok to sort a list of overlays destructively? Marcin Borkowski
2021-07-27  9:40 ` tomas
2021-07-27 10:07   ` Marcin Borkowski
2021-07-27 13:49 ` Eli Zaretskii
2021-07-27 20:14   ` Marcin Borkowski
2021-07-28  2:25     ` Eli Zaretskii
2021-07-28  6:06       ` Marcin Borkowski
2021-07-28 11:44         ` Eli Zaretskii
2021-07-29 11:34           ` John Yates
2021-07-29 12:33             ` Eli Zaretskii
2021-07-29 15:11               ` 2QdxY4RzWzUUiLuE
2021-07-29 15:30                 ` Eli Zaretskii
2021-07-29 16:20                   ` 2QdxY4RzWzUUiLuE
2021-07-29 16:53                     ` Eli Zaretskii [this message]
2021-07-30 19:27               ` Marcin Borkowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83eebhrrie.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.