From: Matt Armstrong <matt@rfc20.org>
To: Michael Kleehammer <michael@kleehammer.com>, 59068@debbugs.gnu.org
Subject: bug#59068: 29.0.50; noverlay causing indirect append issues
Date: Mon, 07 Nov 2022 15:25:27 -0800 [thread overview]
Message-ID: <87y1smmjo8.fsf@rfc20.org> (raw)
In-Reply-To: <CAJmVnVJPk06im+vdOf-yuyE7Evd121pULHhDtgFhajvkBgO+Kw@mail.gmail.com>
Michael Kleehammer <michael@kleehammer.com> writes:
> I compiled master at b7a76f288cc
Hi Michael, can you attempt to reproduce after pulling newer code?
The revision you tested at does not contain recent bug fixes. See this
list, in particular the last commit listed. The symptoms you describe
are consistent with the kinds of weird things that occurred before the
bug#58928 fix.
35221a7bd5 ((itree_insert_gap, itree_delete_gap): Minor optimization, 2022-11-07)
23dd27a979 (itree.c and buffer-tests.el: Incorporate code review feedback, 2022-11-05)
26d2ac38e9 (Minor tweaks to the fix for `insert-before-markers' overlay fix, 2022-11-04)
26460328bc (Fix the unexec build, 2022-11-05)
5e7d08ae13 (itree.c: Minor tightening, 2022-11-03)
ff679e16f8 (itree: Reproduce markers's behavior more faithfully (bug#58928), 2022-11-03)
a66280162f (Port interval trees to --enable-checking=structs, 2022-11-02)
8a5678906f (src/buffer.c: Fix interaction between overlays & indirect buffers (bug#58928), 2022-11-01)
Like Gerd, I was not able to reproduce a problem using newer code.
next prev parent reply other threads:[~2022-11-07 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 5:09 bug#59068: 29.0.50; noverlay causing indirect append issues Michael Kleehammer
2022-11-06 5:25 ` Gerd Möllmann
2022-11-06 6:37 ` Eli Zaretskii
2022-11-07 5:42 ` Michael Kleehammer
2022-11-07 6:59 ` Gerd Möllmann
2022-11-07 23:25 ` Matt Armstrong [this message]
2022-11-16 22:04 ` Michael Kleehammer
2022-11-17 0:28 ` Matt Armstrong
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=87y1smmjo8.fsf@rfc20.org \
--to=matt@rfc20.org \
--cc=59068@debbugs.gnu.org \
--cc=michael@kleehammer.com \
/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.