From: Ihor Radchenko <yantar92@posteo.net>
To: 59067@debbugs.gnu.org
Subject: bug#59067: 29.0.50; Exexpected overlay order in `overlays-in' return value
Date: Sun, 06 Nov 2022 03:39:06 +0000 [thread overview]
Message-ID: <871qqgn44l.fsf@localhost> (raw)
Hi,
Some Org tests are failing when testing with the latest Emacs 29 master.
To reproduce, get the latest Org from git and run make test.
The common feature of all the failing tests is usage of overlays-in and
expecting certain order of overlays in its return value. The order is
changed compared to Emacs 28.
I consider this an Emacs bug.
In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.34, cairo version 1.16.0) of 2022-11-06 built on localhost
Repository revision: 6e5ec085510ccf52ac6cb07c3a1a2778324a1d89
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101004
System Description: Gentoo Linux
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next reply other threads:[~2022-11-06 3:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 3:39 Ihor Radchenko [this message]
2022-11-06 6:26 ` bug#59067: 29.0.50; Exexpected overlay order in `overlays-in' return value Eli Zaretskii
2022-11-06 7:04 ` Ihor Radchenko
2022-11-06 7:16 ` Eli Zaretskii
2022-11-07 23:47 ` Matt Armstrong
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=871qqgn44l.fsf@localhost \
--to=yantar92@posteo.net \
--cc=59067@debbugs.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.