all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vladimir Kazanov <vekazanov@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: The overlay branch (yet again)
Date: Tue, 3 Dec 2019 15:35:17 +0000	[thread overview]
Message-ID: <CAAs=0-05DAsqZwugGweuNVVzbOTBs94gGRHoHxMjC7vC2Cte3w@mail.gmail.com> (raw)
In-Reply-To: <CAAs=0-0o+hnn2=8N7v7Dq-3nQinraOwt+nU5Jsp4jHQBu3xyfw@mail.gmail.com>

Hi all again,

I went through the code written by Andreas Politz (in the
feature/noverlay branch) and all of the related discussions. He
completed an astonishing amount of work! Apart from changes to the
working code the branch includes 1300 LOC of manually written
overlay-related tests, 5700 LOC of automatically generated unit tests
and C-level interval tree tests. Check test/src/buffer-tests.el in the
feature/noverlay branch for reference.

It would be a waste to just throw all of that away. As a first step I
really want to put those tests to work.

Given that nobody replied to my original email I assume everybody is
busy with the new release. In the meantime I'd really like to try to
pick up the work already done on overlays. I have a following plan:

1. A separate patch containing all those tests.
2. A second patch, making overlay code independent from the underlying
implementation.
3. A third patch, providing a tree-based data structure using either
what Andreas built, or smth else.

The first patch should be fairy trivial: I'll extract overlay-specific
tests into a overlay-test.el (while attributing all of the changes to
Andreas, of course), clean up a bit and drop C-level tests. I believe
those tests are really useful the way they are right now and can be
merged separately.

Having those tests merged it will be much easier to go on with further
overlay-related changes (i.e. tweaking internal APIs, or underlying
data structures).

Is anybody interested in me doing this work?

On Tue, Nov 26, 2019 at 2:44 PM Vladimir Kazanov <vekazanov@gmail.com> wrote:
>
> Hi all,
>
> a few years ago I tried replacing the underlying overlay data
> structure with a tree-based one. Back then I ran out of spare time and
> had to delay the project.
>
> I'll have time on my hands this winter and would like to get back to
> the project again. This time it seems that most of the work was done
> by Andreas Politz in the feature/noverlay branch:
>
> https://lists.gnu.org/archive/html/emacs-devel/2018-03/msg00565.html
> https://lists.gnu.org/archive/html/emacs-devel/2019-09/msg00543.html
>
> It seems reasonable to pick up the branch and try to finish it, unless
> somebody is already working on it. So my questions are:
>
> is anybody working on the branch? why was it abandoned? Are there any
> known problems with it?
>
> Thank you
>
> --
> Yours sincerely,
>
>
> Vladimir Kazanov



-- 
Yours sincerely,


Vladimir Kazanov


--
С уважением,

Владимир Казанов



  reply	other threads:[~2019-12-03 15:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 14:44 The overlay branch (yet again) Vladimir Kazanov
2019-12-03 15:35 ` Vladimir Kazanov [this message]
2019-12-03 15:58   ` Eli Zaretskii
2019-12-03 16:06   ` martin rudalics
2019-12-03 16:21     ` Vladimir Kazanov
2019-12-03 17:58       ` Stefan Monnier
2019-12-03 20:46         ` Vladimir Kazanov
2019-12-03 22:43           ` Stefan Monnier
2019-12-04 11:41             ` Vladimir Kazanov
2019-12-05 14:13               ` Vladimir Kazanov
2019-12-05 15:14                 ` Eli Zaretskii
2019-12-05 15:31                   ` Vladimir Kazanov
2019-12-05 16:38                     ` Eli Zaretskii
2019-12-06  6:48                       ` Vladimir Kazanov
2019-12-09  8:10                         ` Vladimir Kazanov

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='CAAs=0-05DAsqZwugGweuNVVzbOTBs94gGRHoHxMjC7vC2Cte3w@mail.gmail.com' \
    --to=vekazanov@gmail.com \
    --cc=emacs-devel@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.