Re: Question collaborative editing - Wikipedia reference

[Eli Zaretskii]

> From: Qiantan Hong <qhong@mit.edu>
> CC: Joe Corneli <holtzermann17@gmail.com>,
>         "joakim@verona.se"
>       <joakim@verona.se>, Yuan Fu <casouri@gmail.com>,
>         Fermin <fmfs@posteo.net>, Jean Louis <bugs@gnu.support>,
>         Caio Henrique <caiohcs0@gmail.com>, Ergus
>       <spacibba@aol.com>,
>         Noam Postavsky <npostavs@gmail.com>, Karl Fogel
>       <kfogel@red-bean.com>,
>         Stefan Monnier <monnier@iro.umontreal.ca>,
>         emacs-devel
>       <emacs-devel@gnu.org>
> Date: Sun, 11 Oct 2020 19:57:43 +0000
> 
> (Part of) it can be done there if we’ve decided on “how to filter”.
> In the current way doing so is not required. But the question is
> “how to filter”.
> 
> Let the user providing an arbitrary predicate (overlay->bool) seems to be
> the most canonical, but it’s not. How to compose multiple predicates
> provided by user? Or we can just let user do it and accept only one predicate.
> But even so, apparently one piece of information missing is where the
> overlay comes from. Lots of command don’t assign any ‘category
> to the overlay their created and it’s hard to tell what the overlay is for
> just by looking at the overlay object. In fact, currently I don’t use
> any user provided predicate and filter solely based on what command
> creates the overlay (by advising it to add a ‘crdt-meta property) and it
> works well for org-mode folding, but I’m not sure if that works in other
> scenarios.

Let me turn the table and ask why did you think there's a need to send
information about overlays and text properties over the wire?  What
were the use cases where you thought this would be necessary?