From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Concurrency via isolated process/thread Date: Sun, 09 Jul 2023 10:04:38 +0000 Message-ID: <87jzv98kp5.fsf@localhost> References: <871qhnr4ty.fsf@localhost> <874jmh6v4s.fsf@localhost> <83y1jtgmbw.fsf@gnu.org> <87zg49xfke.fsf@localhost> <83sfa1gjns.fsf@gnu.org> <87r0plxbep.fsf@localhost> <83ilawhpi6.fsf@gnu.org> <87zg48apwr.fsf@localhost> <83edljg8ub.fsf@gnu.org> <87o7knbxr7.fsf@localhost> <838rbrg4mg.fsf@gnu.org> <87ilavbvdr.fsf@localhost> <834jmffvhy.fsf@gnu.org> <878rbrbmwr.fsf@localhost> <83fs5zecpo.fsf@gnu.org> <87351zbi72.fsf@localhost> <83351yevde.fsf@gnu.org> <87cz12ad2w.fsf@localhost> <83a5w6cwdr.fsf@gnu.org> <87pm518m0g.fsf@localhost> <87cz11e7cs.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4692"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jul 09 12:05:09 2023 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 1qIRHx-000104-3K for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Jul 2023 12:05:09 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qIRHR-0006eT-E1; Sun, 09 Jul 2023 06:04:37 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qIRHP-0006eK-TO for emacs-devel@gnu.org; Sun, 09 Jul 2023 06:04:36 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qIRHN-0006Fr-Sf for emacs-devel@gnu.org; Sun, 09 Jul 2023 06:04:35 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 43A3B240106 for ; Sun, 9 Jul 2023 12:04:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1688897072; bh=A6hiz1OHAavhyRQYpDJfJdU91jO8Odjp0ZD47vZn6yg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=EA0s471ERpEjHodtcnJTKVOYY7/0HjsMpgaRCFtR/KYQKs+Rz4Nkah8iUjL2rCeRr c5cqcF9G6ii4V6C4ckRJUhxl0mfFklrLWdni6Tl85d3g6ZtK/eDKLAX5Q5UcfjGyyP lQVacMbiBuvpymfHasUsYqcHwiaVNCln+veHvNkryYM66f7M/qKF9bHbY2Jo6ZOjD6 54aB8Kkz3uuKK+/wXk4yJ6LE3IPpCioy2y33nmHhDI4z/FGJ6NA5XJzHEoz63z+yhk HwVR9Z+s089bFi/U1hDkOz3xiJ3XM62u48c+oNMG3vs7kfY5ud3RWT6XiYfcWVFIWL E4EjJddnItkVg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QzN5q4SDHz6tyT; Sun, 9 Jul 2023 12:04:31 +0200 (CEST) In-Reply-To: <87cz11e7cs.fsf@yahoo.com> Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:307658 Archived-At: Po Lu writes: > Ihor Radchenko writes: > >> Am I missing something, does the gap remain intact when the just move >> point? AFAIU, the gap only needs to move when we do edits. >> >> I was thinking about thread-local variables just to move around and read >> buffer. Asynchronous writing is probably a poor idea anyway - the very >> idea of a gap does not work well when we need to write in multiple >> far-away places in buffer. > > Thread-local state is NOT cheap! We should not jump at every > opportunity to add new thread-local state. I see. I still think that adding PT, BEGV, and ZV makes sense (even for current cooperative threads; I have been trying to write something using these some time ago, and having to constantly switch buffer and set point was a big annoyance). As for global C variable bindings, may we get rid of them? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at