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: Concurrency via isolated process/thread Date: Mon, 10 Jul 2023 17:37:44 +0300 Message-ID: <83ilar96iv.fsf@gnu.org> 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> <87y1jn6f6v.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12624"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, luangruo@yahoo.com, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jul 10 16:38:30 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 1qIs21-00032d-GN for ged-emacs-devel@m.gmane-mx.org; Mon, 10 Jul 2023 16:38:29 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qIs1C-0000s2-Fi; Mon, 10 Jul 2023 10:37:38 -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 1qIs1A-0000re-TS for emacs-devel@gnu.org; Mon, 10 Jul 2023 10:37:36 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qIs19-0007n5-Cv; Mon, 10 Jul 2023 10:37:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=2Y3tkIcKKivEN2OYxqRT0oDGY5PUZAPjFN2SC1kNc7o=; b=CM/nLxTvOmAu QQRMmYqrsmSFtf5zKMI5kTcoJBJrZREvgN4gziOaEjSsBFVb9KwQcEIkTE6dsGSoz+w7ahxcr9e5W /gdrbreIxegK2cDhLZF4p6+7ozXSDKxP/5DERXJvSZZqKo1MHN22fHLerVcJJ7KDjqHTaXiEAVDjk vBde5x5T42VCgOn/yUZhw+D7Jt3Cr6XyxfvnBrICjXrldXt+vprs3moJZqtMixTnNVtJK5G7vrErg jgOlOSckwt8vebDgstbtPjpUWFOV3dEM/GlPdE/cS1k8MMWGq35kDK3iPC5EEUpidQyzSwRCjxUr8 5pPK2xpvs1KACcSQ8au2qQ==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qIs18-0004P7-TE; Mon, 10 Jul 2023 10:37:35 -0400 In-Reply-To: <87y1jn6f6v.fsf@localhost> (message from Ihor Radchenko on Mon, 10 Jul 2023 13:58:48 +0000) 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:307723 Archived-At: > From: Ihor Radchenko > Cc: monnier@iro.umontreal.ca, luangruo@yahoo.com, emacs-devel@gnu.org > Date: Mon, 10 Jul 2023 13:58:48 +0000 > > 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? You are asking questions that would require me to do a lot of code scanning and investigating to produce a full answer. So please forgive me if I can afford only some random examples that pop up in my mind, not even close to the exhaustive list: . the window tree (redisplay traverses it depth-first) . point position of displayed buffers (needed to decide whether to scroll the window) . narrowing of each displayed buffer . text properties and overlays of each displayed buffer . which window is selected on each frame . window-start position of each window . variables affecting display: display-line-numbers, show-trailing-whitespace, line-spacing, auto-compression-mode, auto-hscroll-mode, mode-line-format, etc. And that is just a few seconds of thinking, I'm sure I forget a lot of others.