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 14:55:36 +0000 Message-ID: <87v8er6ck7.fsf@localhost> References: <871qhnr4ty.fsf@localhost> <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> <83ilar96iv.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="24322"; 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 16:56:07 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 1qIsJ0-0005wb-FD for ged-emacs-devel@m.gmane-mx.org; Mon, 10 Jul 2023 16:56:02 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qIsIh-0007ml-DS; Mon, 10 Jul 2023 10:55:43 -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 1qIsIf-0007iX-Fv for emacs-devel@gnu.org; Mon, 10 Jul 2023 10:55:41 -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 1qIsIc-0006CI-0Y for emacs-devel@gnu.org; Mon, 10 Jul 2023 10:55:41 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 25498240106 for ; Mon, 10 Jul 2023 16:55:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1689000933; bh=1+52Kuk7HrRM3cbMXjwurAf6MNXciHXRQGDjMYVUQuI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=jjfi2+7xmiN4vTaKJ9srNIj5RPCwqGognpnzZqJ77DYCsqjQgIev04UPE/lFvAzu9 qgN9NQSBK4SnK4hCO0MOtirkFSVInC1Zr1avIGfvE7uRZfyns4hfCNq61YBv1+QhJ6 unlg67/X4hpa0EAj1xMEZitNhA5jGO46r/GVMWhJ+0SO7RrvggFKXIs8MZGX1w/JlE GB5x3FGkjguIS2w1My4rkg2YvAQt9w9utVhySzMjL1l3AMY8lSYsYgYDSFK1yhR4Bo S/RT2CPEeT9yljEatrUmMuk4DThYbGudn45AL/PPrScG7u2tmFnrDkCouaxQHKB6rA Q20OgL4O8TSIQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4R06W82j9tz9rxL; Mon, 10 Jul 2023 16:55:32 +0200 (CEST) In-Reply-To: <83ilar96iv.fsf@gnu.org> 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:307726 Archived-At: Eli Zaretskii writes: >> 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: Thanks, that is good enough. I mostly wanted to get pointers to interesting places in that 1.2Mb xdisp.c file to save myself from reading it from top to bottom. > . the window tree (redisplay traverses it depth-first) > . point position of displayed buffers (needed to decide whether to > scroll the window) Maybe point position in 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. These lay in 4 categories: 1. Data attached to frame object (window tree) 2. Data attached to window object (point position, window-start, etc) 3. Data attached to buffer object (buffer-local variables, narrowing) 4. Global Lisp variables I have a suspicion that at least windows in a frame might be redisplayed in parallel, unless some strange Elisp code is allowed to modify things affecting redisplay. May I know what happens if redisplay code sets variables like line-spacing or display-line-numbers? Is it allowed? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at