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 14:16:31 +0000 Message-ID: <871qhh891c.fsf@localhost> References: <871qhnr4ty.fsf@localhost> <87bkgq8p5t.fsf@localhost> <831qhmjwk0.fsf@gnu.org> <875y6y8nlr.fsf@localhost> <87h6qhnalc.fsf@yahoo.com> <87ilax71wo.fsf@localhost> <831qhli14t.fsf@gnu.org> <87wmzdxewc.fsf@localhost> <83r0plgjeo.fsf@gnu.org> <87o7kpxapo.fsf@localhost> <83mt09gcaf.fsf@gnu.org> <87wmzbc3af.fsf@localhost> <83cz13g811.fsf@gnu.org> <87lefrbvjw.fsf@localhost> <83h6qfecxt.fsf@gnu.org> <875y6vbiej.fsf@localhost> <834jmeew2u.fsf@gnu.org> <87a5w6aa89.fsf@localhost> <838rbqcvlx.fsf@gnu.org> <87mt058l1b.fsf@localhost> <83mt059tir.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24860"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jul 09 16:17:13 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 1qIVDt-0006G8-26 for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Jul 2023 16:17:13 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qIVDO-0001rY-T5; Sun, 09 Jul 2023 10:16:42 -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 1qIVDN-0001qx-1O for emacs-devel@gnu.org; Sun, 09 Jul 2023 10:16:41 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qIVDG-0007FI-UA for emacs-devel@gnu.org; Sun, 09 Jul 2023 10:16:36 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 46238240029 for ; Sun, 9 Jul 2023 16:16:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1688912192; bh=4FZg/3hq5wpG/OkUpKkHy6X2bTIC9r7ifB8c0jRoxfM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=aDKHVHHL1MFilrkYt0d8X8Cqab+WsqXKfMfi5t2DQZV7tcVfhUL2WsgWaHMq6rZeT zjMk89mPX+ePIkn71KdI8+VL1Yrs7gA3b6CsOeg/AQjokJ7jmkxvVSYlzW1uHnyr98 FglztkBSqj+OlNq3YYPdhedfBQ7xgzfDFwGpP/D02BM5cryz1q1UQsGR+6rhQrXlds 1t+EK7onRF4yvX3/tUFKR1XcewByEYe6brkFZYdv2pOBZcTCjm0mDynahXTRQR43GB lMDJ85wUxw8SGysx9dADM6YK4q5ZQFzw0gN1gQfiIZIivkAhr5wbFqoc84umfwls7q cncU8S8NIfPJA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QzThY59kBz6tv5; Sun, 9 Jul 2023 16:16:29 +0200 (CEST) In-Reply-To: <83mt059tir.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -53 X-Spam_score: -5.4 X-Spam_bar: ----- X-Spam_report: (-5.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=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable 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:307683 Archived-At: Eli Zaretskii writes: >> Of course, if there are breaking future changes on C level will need to >> account for concurrency. > > Who will remember that we at some point "assumed" buffer->base_buffer > can change _only_ in make-indirect-buffer? Ok. So, in other words, we need to make sure that any changes in a buffer and also in indirect buffers will lock. Trying to be more granular is not reliable. >> So, redisplay will have access to correct local values. > > No, it won't, because redisplay runs only in the main thread, > remember? So it will not see changes to Vfoo done by other threads. > This could sometimes be good (e.g., if the changes are temporary), but > sometimes bad (if the changes are permanent). If redisplay is about to display buffer that is being modified (including its buffer-local values), it will have to lock until the modification is done. Same for global Lisp variables. >> > What do you expect redisplay to do when some thread moves point in a >> > way that it is no longer in the window? >> >> Async threads will not trigger redisplay. And they will have their own >> PT, BEGV, and ZV. > > This goes back to the other sub-thread, where we discussed how to show > and prompt the user from non-main threads. The conclusion was that > there is no good solution to that. The best proposal, wait for the > main thread, would mean that stuff like stealth fontifications, which > currently run from timers, cannot be run from a thread. May you provide a link? I am not sure how independent PT+buffer in different threads affects prompts. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at