From: 2QdxY4RzWzUUiLuE@potatochowder.com
To: help-gnu-emacs@gnu.org
Subject: Re: Is it ok to sort a list of overlays destructively?
Date: Thu, 29 Jul 2021 09:20:21 -0700 [thread overview]
Message-ID: <YQLVRZrk8bcrQpDt@scrozzle> (raw)
In-Reply-To: <83im0trvbq.fsf@gnu.org>
On 2021-07-29 at 18:30:49 +0300,
Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Thu, 29 Jul 2021 08:11:46 -0700
> > From: 2QdxY4RzWzUUiLuE@potatochowder.com
> >
> > > > I am not sure if such a statement exists in any of the manuals. Should
> > > > it not be stated explicitly somewhere?
> > >
> > > I don't think it should be, no. It's pretty much obvious, IMO.
> >
> > I'm not disagreeing, but why is it obvious?
>
> 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.
I don't realize the expectation you mentioned unless/until I think of
Emacs as platform of some kind, upon which I build a program. To that
end, https://www.gnu.org/software/emacs/ does now claim that "[a]t its
core is an interpreter for Emacs Lisp, a dialect of the Lisp programming
language with extensions to support text editing."
I'm definitely closer to "it's obvious" than I was earlier. :-)
My descriptionb of overlays-in (I don't have the C source code handy,
only what appears when I run describe-function in Emacs 27.2) matches
Marcin's and doesn't describe sorting.
next prev parent reply other threads:[~2021-07-29 16:20 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 [this message]
2021-07-29 16:53 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YQLVRZrk8bcrQpDt@scrozzle \
--to=2qdxy4rzwzuuilue@potatochowder.com \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).