Closed flexibeast closed 9 years ago
This is mostly documented in lentic.el, but will put something in README.md.
indirect-buffers are fundamentally broken because they share both text and text-properties. With lentic buffers you can choose what to share (by default only text). You don't even have to have identical text in both buffers.
Thanks. :-) Yeah, on lentic
s page on MELPA, the commentary in lentic.el
is displayed; but i first encountered lentic
via its main GitHub page, where README.md still refers to "linked-buffer" in various ways. (Fwiw, i've started using el2markdown
to keep my "Commentary" section and README.md in sync, even though doing so results in some ugly effects on packages' MELPA pages.)
I have missed the README in the rename search and replace!
Keeping two sources files in sync and in git is, of course, the worst thing about using something both as a website AND as a version control system. I'll update the readme soon, and link through to the HTML source.
It might be useful to list the advantages
lentic
provides over Emacs' built-in "indirect buffers" functionality.