From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@newcastle.ac.uk (Phillip Lord)
Cc: spinuvit@gmail.com, monnier@iro.umontreal.ca,
drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: Indirect buffers
Date: Mon, 09 Jun 2014 17:41:07 +0300 [thread overview]
Message-ID: <8361ka2lj0.fsf@gnu.org> (raw)
In-Reply-To: <877g4q1hpa.fsf@newcastle.ac.uk>
> From: phillip.lord@newcastle.ac.uk (Phillip Lord)
> Cc: Drew Adams <drew.adams@oracle.com>, Vitalie Spinu <spinuvit@gmail.com>, Stefan Monnier <monnier@iro.umontreal.ca>, <emacs-devel@gnu.org>
> Date: Mon, 09 Jun 2014 11:49:05 +0100
>
> Forgive the plug, but this is exactly how my own linked-buffer works.
>
> https://github.com/phillord/linked-buffer/
>
> It works fine and is performant enough for smallish files; I haven't
> tried it for much larger ones yet. This is with a very dumb
> implementation (the whole buffer is copied on the after change hook).
>
> The big advantage over indirect buffers is that I control the way in
> which text in the two buffers is related; if this is `buffer-string'
> you'd get the same as indirect-buffers (although less efficiently). If
> you use the no-properties version, then you get something like
> indirect-buffers but multi-modes work. If you use an function which
> changes the text, then you can support two modes with incompatible
> syntaxes. No support at all is needed from the modes.
Thanks for the pointer. I indeed wondered how was it possible that no
one came up with such a simple idea, so now I'm happy I was wrong.
next prev parent reply other threads:[~2014-06-09 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 15:53 bug#17738: 24.4.50; (jit-lock-mode nil) in indirect buffer: wrong message Drew Adams
2014-06-08 16:39 ` Indirect buffers Eli Zaretskii
2014-06-09 10:49 ` Phillip Lord
2014-06-09 14:41 ` Eli Zaretskii [this message]
2016-04-29 20:44 ` bug#17738: 24.4.50; (jit-lock-mode nil) in indirect buffer: wrong message Lars Ingebrigtsen
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=8361ka2lj0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=phillip.lord@newcastle.ac.uk \
--cc=spinuvit@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 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.