From: Matt Armstrong <matt@rfc20.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: 57150@debbugs.gnu.org
Subject: bug#57150: 29.0.50; [PATCH] Add test coverage for overlay modification hooks
Date: Sat, 13 Aug 2022 17:44:59 -0700 [thread overview]
Message-ID: <87zgg7fyb8.fsf@rfc20.org> (raw)
In-Reply-To: <878rns946i.fsf@localhost>
Ihor Radchenko <yantar92@gmail.com> writes:
> Matt Armstrong <matt@rfc20.org> writes:
>
>> I noticed there was no explicit test against the overlay modification
>> hook boundary conditions. The attached patch adds some, which might be
>> nice to have if a person (possibly me) someday optimizes overlay
>> performance with a change in data structure.
>
> Just in case. Have you seen
> https://lists.gnu.org/archive/html/emacs-devel/2019-12/msg00323.htlm
> ?
>
> I am not sure how much progress have been made on the noverlay branch,
> but there was at least some existing test suitcase in there. Not sure if
> it has been merged or if your proposed patch is not covered.
Yes, thank you for pointing that out. I have gone as far as importing
the entire history of emacs-devel into https://notmuchmail.org/ and read
as much history about the overlay problem as I could discover.
I have been in contact with both Andreas (the original feature/noverlay
author) and Vladimir (who later examined it). Andreas had no plans to
return to looking at the problem and did not recall the precise state
the branch was left in. Vladimir, despite his interest, was
unfortunately not able to get his employer to sign FSF papers. Both
wished me luck.
Fortunately all of the test cases from the feature/noverlay branch were
merged to the master branch, I believe by Eli, shortly after they were
written years ago.
As for feature/noverlay itself, I have been exploring alternative
approaches that might be simpler or clearer than Andreas' approach, with
the clear advantage of seeing his implementation, of course. Failing
any improvement I can always start right where he left off.
next prev parent reply other threads:[~2022-08-14 0:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 4:32 bug#57150: 29.0.50; [PATCH] Add test coverage for overlay modification hooks Matt Armstrong
2022-08-12 4:41 ` Matt Armstrong
2022-08-12 6:19 ` Eli Zaretskii
2022-08-12 17:57 ` Matt Armstrong
2022-08-12 18:53 ` Eli Zaretskii
2022-08-14 4:52 ` Matt Armstrong
2022-08-14 7:15 ` Eli Zaretskii
2022-09-04 21:59 ` Lars Ingebrigtsen
2022-08-13 4:07 ` Ihor Radchenko
2022-08-14 0:44 ` Matt Armstrong [this message]
2022-08-15 4:14 ` Ihor Radchenko
2022-08-15 11:26 ` Eli Zaretskii
2022-08-17 2:50 ` Richard Stallman
2022-08-17 10:05 ` Ihor Radchenko
2022-08-17 11:51 ` 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
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=87zgg7fyb8.fsf@rfc20.org \
--to=matt@rfc20.org \
--cc=57150@debbugs.gnu.org \
--cc=yantar92@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).