From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Question collaborative editing - Wikipedia reference Date: Mon, 12 Oct 2020 05:26:39 +0300 Message-ID: <838scc41sw.fsf@gnu.org> References: <83eemji6e8.fsf@gnu.org> <20201001141144.GO4797@protected.rcdrun.com> <20201001160136.chwmpollk4d3qc2e@Ergus> <20201004175447.GG15516@protected.rcdrun.com> <87362tvnil.fsf@gmail.com> <20201004194815.GH15516@protected.rcdrun.com> <11EB917D-3276-4D34-8DCD-2336E8062950@mit.edu> <20201005040245.GJ15516@protected.rcdrun.com> <20201005084441.GB4453@protected.rcdrun.com> <87zh50lhda.fsf@red-bean.com> <87pn5vgqsk.fsf@red-bean.com> <79924DB1-2613-4AF6-982C-39157CF3ED9B@mit.edu> <8C2D2AED-0AA8-48AC-ADB2-826177141F2F@gmail.com> <40B06E9F-A6D6-4F9B-8E2B-7DC55D16D0F7@mit.edu> <18458910-E6A1-4867-9936-FFA50E3E72D1@gmail.com> <4AB5904E-A646-4A17-B78C-B4E0271E28B4@mit.edu> <87imbjx0bm.fsf@tanaka.verona.se> <80512E57-D3BA-4F02-A835-DEE434278736@mit.edu> <83blh84o8w.fsf@gnu.org> <83a6ws4mns.fsf@gnu.org> <4C6C49B0-68A8-402C-9BC0-1FB11BD8A9F3@mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29680"; mail-complaints-to="usenet@ciao.gmane.io" Cc: casouri@gmail.com, fmfs@posteo.net, bugs@gnu.support, caiohcs0@gmail.com, spacibba@aol.com, joakim@verona.se, npostavs@gmail.com, kfogel@red-bean.com, monnier@iro.umontreal.ca, holtzermann17@gmail.com, emacs-devel@gnu.org To: Qiantan Hong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 12 04:27:15 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kRnYR-0007cz-Nu for ged-emacs-devel@m.gmane-mx.org; Mon, 12 Oct 2020 04:27:15 +0200 Original-Received: from localhost ([::1]:50630 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kRnYQ-0007k7-Qc for ged-emacs-devel@m.gmane-mx.org; Sun, 11 Oct 2020 22:27:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48452) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kRnXu-0007Kn-1U for emacs-devel@gnu.org; Sun, 11 Oct 2020 22:26:42 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33978) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kRnXp-0006HD-3h; Sun, 11 Oct 2020 22:26:37 -0400 Original-Received: from [176.228.60.248] (port=4149 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kRnXn-0003N1-Rr; Sun, 11 Oct 2020 22:26:36 -0400 In-Reply-To: <4C6C49B0-68A8-402C-9BC0-1FB11BD8A9F3@mit.edu> (message from Qiantan Hong on Sun, 11 Oct 2020 19:57:43 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:257437 Archived-At: > From: Qiantan Hong > CC: Joe Corneli , > "joakim@verona.se" > , Yuan Fu , > Fermin , Jean Louis , > Caio Henrique , Ergus > , > Noam Postavsky , Karl Fogel > , > Stefan Monnier , > emacs-devel > > 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?