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, 24 Jul 2023 13:15:55 +0000 Message-ID: <87r0ox1md0.fsf@localhost> References: <871qhnr4ty.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> <83o7kl9tyj.fsf@gnu.org> <874jmd89us.fsf@localhost> <878rb53dkj.fsf@localhost> <87wmyp1vr9.fsf@yahoo.com> <875y6939jl.fsf@localhost> <83cz0hscbp.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="24879"; 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 Mon Jul 24 15:17:02 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 1qNvQq-0006Cg-QC for ged-emacs-devel@m.gmane-mx.org; Mon, 24 Jul 2023 15:17:00 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qNvPm-0006aB-AB; Mon, 24 Jul 2023 09:15:54 -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 1qNvPj-0006ZT-TQ for emacs-devel@gnu.org; Mon, 24 Jul 2023 09:15:52 -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 1qNvPf-00055s-En for emacs-devel@gnu.org; Mon, 24 Jul 2023 09:15:51 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id C9C73240101 for ; Mon, 24 Jul 2023 15:15:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1690204542; bh=M75OOOgOqnyGH2bj7UqXxD5HrQIdQqS4lB41BLIGy/g=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=erz3fgpOvRRClSE1Mp/LB8PWXkNtKvMq+VO1GHgMaauMxOp0Ptoc4Hzxg/eHfoRY9 Yx8mcEbnJ8Fx8Zu7Ih2tnVvsrUXKn233N4hcfYbqHd/tgHRwR3lEwpbuMUWEtTM5EK 7uNzO/HxNFoQ5vQPganmEcNM8a8nbgMuFw5GjD4MS8XWRpoPodlVq+Q5CB68Lc3iNQ Vv84tDM/RVTE3PG1nxnfI6P6hr6sfrKVgOPSOW0qcOIEMLHuO5uS1fkbBBeh7I5FwF tJVCK8jQlz+reZDZWzwMBk8mQfPu6821HMLgVwkSWGbQjuMQlEkYVy42h8d5P+qZ90 Uaei7wQNb0EEQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4R8gdV0yBwz6tn4; Mon, 24 Jul 2023 15:15:41 +0200 (CEST) In-Reply-To: <83cz0hscbp.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=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:308056 Archived-At: Eli Zaretskii writes: >> The basic idea is to have >> #define PT (current_thread->m_pt + 0) >> #define PT_BYTE (current_thread->m_pt_byte + 0) > > Point is the attribute of a buffer. The current definition of PT, > viz.: > > #define PT (current_buffer->pt + 0) > > automagically makes PT refer to the current buffer, so the code only > needs to change current_buffer to have PT set correctly. > > By contrast, you propose to have one value of point per thread, which > means a thread that switches buffers will have to manually change all > of these values, one by one. Why is that a good idea? Switching buffer already involves juggling with pt_marker_ in record_buffer_markers and fetch_buffer_markers. So, I do not see much problem here. > And what about C code which copies/moves text between two buffers? > For example, some primitives in coding.c can decode text from one > buffer while writing the decoded text into another. They still use set_buffer_internal. There are certain cases when the code needs to fetch buffer point from a buffer that is not current, but I did not yet look into them closely before asking if the whole idea is going to be acceptable. (Roughly, I plan to use thread point history or fallback to default point position as in buffer constructor). -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at