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: Mon, 10 Jul 2023 13:58:48 +0000 Message-ID: <87y1jn6f6v.fsf@localhost> References: <871qhnr4ty.fsf@localhost> <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> <83o7kl9tyj.fsf@gnu.org> <874jmd89us.fsf@localhost> <83cz119lxu.fsf@gnu.org> <87v8et6q5m.fsf@localhost> <838rbp9h6c.fsf@gnu.org> <87edlg6m2l.fsf@localhost> <83o7kj9alq.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="9720"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, 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 Mon Jul 10 15:59:39 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 1qIrQQ-0002GK-2G for ged-emacs-devel@m.gmane-mx.org; Mon, 10 Jul 2023 15:59:38 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qIrPd-00071E-Ue; Mon, 10 Jul 2023 09:58:49 -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 1qIrPc-000710-4e for emacs-devel@gnu.org; Mon, 10 Jul 2023 09:58:48 -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 1qIrPY-0001mS-6j for emacs-devel@gnu.org; Mon, 10 Jul 2023 09:58:47 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 82501240029 for ; Mon, 10 Jul 2023 15:58:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1688997521; bh=v97ead5LO5yDGTpMnGLjS1YLEhIvsbRG+uoAADcV2L0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=CS37xpK/yjhqXK9lWfwshqzb55/FNmUKkxXGC+BHbgaDhyzr/AX8Cfgdw97WCcD6M 2XsXK1rcY4fiqucWV1G4xsauZMVUwEb0iRsLv8MshkB1kmKuHa4nrS6gbXmFihZ4Uj v6+HML91RG87DNVQFbbIBnJtCgI+8N/FXvPlK/yn15o7NUO3m0t4wHSAYWFggmxiRy aIVEMKUsBK0ZvFU7+rwP29tQgm798ZBElqTLn61xPSpb68ALXUqStm9iSwteD5FSwj ZIeMn1AXzANAKQbu78aNBkLXMVL5Fi1Ebua5llpzjegkng/1cGwbaA7x76CNipKiIU YZJzgqtASH47g== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4R05FX43jPz6twB; Mon, 10 Jul 2023 15:58:40 +0200 (CEST) In-Reply-To: <83o7kj9alq.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: -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=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:307722 Archived-At: Eli Zaretskii writes: >> AFAIU, it is currently not possible to redisplay asynchronously. > > The main reason for that is that redisplay accesses the global state > in many places, and so it needs that global state to stay put. Wed > already have trouble with keeping this so because we allow to run Lisp > from various hooks called by redisplay and via :eval in the mode line. > Quite a few bugs were caused by these, and had to be fixed by "fixing > up" the state, like making sure the selected frame/window were not > deleted under your feet etc. Do you know which particular parts of the global state are necessary for redisplay? You mentioned current_frame and current_window. What else? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at