Re: Indirect buffers

[Eli Zaretskii]

> From: address@hidden (Phillip Lord)
> Cc: Drew Adams <address@hidden>,  Vitalie Spinu <address@hidden>,  Stefan 
> Monnier <address@hidden>,  <address@hidden>
> 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.