unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vladimir Kazanov <vekazanov@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jimjoe@gmx.net, emacs-devel@gnu.org
Subject: Re: Buffers with buffers (transclusion)
Date: Thu, 17 Oct 2024 14:24:10 +0100	[thread overview]
Message-ID: <CAAs=0-2Ue=OgOYGQn+qVSR=DJs-dwHBJUyDofiV2h9g-8QYJMA@mail.gmail.com> (raw)
In-Reply-To: <861q0eq40x.fsf@gnu.org>

Eli,

Thanks, almost convinced and this might be the last question on the
topic I have.

Either way, I'll summarize the discussion, my findings and conclusions
in an email that would wrap up the thread - just for future reference.

> Making the display engine show several buffers is actually very easy,
> technically.  By contrast, the problems I mentioned above are much
> harder, especially since it is not clear conceptually what the
> solutions should be.

So here's the final idea I had. Let's say we introduce a special kind
of relationship between pairs of buffers - a "sync pipe". An example:

(create-sync-pipe left-buffer right-buffer left-beg &optional left-end
right-beg right-end properties bidirectional)

This creates a connection that pushes all changes in one buffer to the
other, and vice versa. Might be limited to certains buffer regions
using (LEFT-BEG LEFT-END), (RIGHT-END, RIGHT-END) regions. Setting
PROPERTIES to (t) would also sync text properties, and BIDIRECTIONAL
means that changes go both ways.

The function will return a special C-level object that can be deleted
with (delete-pipe pipe).

PROPERTIES can be either t, nil or a a list of properties to sync. In
fact, being able to efficiently sync text and properties between
region is already 70% to what I had in mind.

Would you be open to reviewing such a patch?

Thank you

-- 
Regards,

Vladimir Kazanov



  reply	other threads:[~2024-10-17 13:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 13:53 Buffers with buffers (transclusion) Vladimir Kazanov
2024-10-15 14:45 ` Eli Zaretskii
2024-10-15 15:01   ` Vladimir Kazanov
2024-10-16 22:44     ` James Thomas
2024-10-17  6:27       ` Eli Zaretskii
2024-10-17  8:38         ` Vladimir Kazanov
2024-10-17 11:00           ` Eli Zaretskii
2024-10-17 11:38             ` Vladimir Kazanov
2024-10-17 12:59               ` Eli Zaretskii
2024-10-17 13:24                 ` Vladimir Kazanov [this message]
2024-10-17 15:15                   ` Eli Zaretskii
2024-10-17 14:36             ` Suhail Singh
2024-10-17 15:19               ` Eli Zaretskii
2024-10-17 16:28                 ` Suhail Singh
2024-10-17 17:18                   ` Eli Zaretskii
2024-10-18  9:25                     ` Vladimir Kazanov
2024-10-17 14:09           ` James Thomas
  -- strict thread matches above, loose matches on Subject: below --
2024-10-15 17:57 Christopher Howard
2024-10-16 10:48 ` 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

  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='CAAs=0-2Ue=OgOYGQn+qVSR=DJs-dwHBJUyDofiV2h9g-8QYJMA@mail.gmail.com' \
    --to=vekazanov@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jimjoe@gmx.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 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).