From: Matt Armstrong <matt@rfc20.org>
To: Eli Zaretskii <eliz@gnu.org>, Ihor Radchenko <yantar92@posteo.net>
Cc: 59067@debbugs.gnu.org
Subject: bug#59067: 29.0.50; Exexpected overlay order in `overlays-in' return value
Date: Mon, 07 Nov 2022 15:47:51 -0800 [thread overview]
Message-ID: <87tu3amimw.fsf@rfc20.org> (raw)
In-Reply-To: <835yfs363u.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> I'll wait for a few days for other ideas and opinions, and if nothing
> pops up, I will amend the documentation (and NEWS, as this is probably
> NEWS-worthy).
I think amending the documentation is the right approach, and agree that
it is NEWS-worthy.
In Emacs git we have already seen one fix related to this issue:
651bf0a999 (Fix overlays order in Flyspell (bug#58970), 2022-11-03)
...with that example, and this one from Org, we can rationally expect
more.
The original overlay implementation happened to provide one ordering,
but it could change when the overlay "center" moved, so packages that
rely on anything specific are on shaky ground.
next prev parent reply other threads:[~2022-11-07 23:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 3:39 bug#59067: 29.0.50; Exexpected overlay order in `overlays-in' return value Ihor Radchenko
2022-11-06 6:26 ` Eli Zaretskii
2022-11-06 7:04 ` Ihor Radchenko
2022-11-06 7:16 ` Eli Zaretskii
2022-11-07 23:47 ` Matt Armstrong [this message]
2022-11-10 10:19 ` Eli Zaretskii
2022-11-10 14:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-10 20:37 ` Dmitry Gutov
2022-11-10 20:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-10 21:00 ` Dmitry Gutov
2022-11-10 21:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-11 2:13 ` Dmitry Gutov
2022-11-11 2:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-11 7:48 ` Eli Zaretskii
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=87tu3amimw.fsf@rfc20.org \
--to=matt@rfc20.org \
--cc=59067@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yantar92@posteo.net \
/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.