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: Sat, 08 Jul 2023 12:01:00 +0000 Message-ID: <877craa9z7.fsf@localhost> References: <871qhnr4ty.fsf@localhost> <87cz16o8vz.fsf@yahoo.com> <87jzve8r4m.fsf@localhost> <871qhmo5nv.fsf@yahoo.com> <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> <87edljhmjq.fsf@yahoo.com> <87fs5zbuwn.fsf@localhost> <871qhjgrku.fsf@yahoo.com> <831qhieumz.fsf@gnu.org> <87lefqg7yl.fsf@yahoo.com> <83h6qed8kw.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="34772"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Po Lu , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jul 08 14:02:00 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 1qI6dU-0008nL-A5 for ged-emacs-devel@m.gmane-mx.org; Sat, 08 Jul 2023 14:02:00 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qI6ce-0006Fb-48; Sat, 08 Jul 2023 08:01:08 -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 1qI6cb-0006Br-Iu for emacs-devel@gnu.org; Sat, 08 Jul 2023 08:01:05 -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 1qI6cV-0002yb-MJ for emacs-devel@gnu.org; Sat, 08 Jul 2023 08:01:04 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 3E452240104 for ; Sat, 8 Jul 2023 14:00:58 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1688817658; bh=E8UnKbujcS9TCic7+GdJs6NO4VzrCPdDwN5tDazKubY=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=HG/0RBrbvFrkRiJDjSfdP16z9saSYnypvDBwHsYUC+U1sgccNqZ45OeWpTpWAyLej NCNdNMRa/g2ZKaN7DhPjVu2Qy5SXZtB89ycAXig+SULsoeGgWqzvF15Rv9l5wCf+wG 0FVZ9vp++R8qgYEz2dmqqcss86pi1fcOb6/KxkVkQYgbwC8qXPU4kKjksmre3/kUGq WSWvGesf1X9F2is+T8ERC6wvVjSIEVOliYvRXRTXzWVlMgjKsxCAYUVs0u49eCObdV JbCWBbmVHEev1L05TleOxFB+XixtKVqIlV6180mq7/G4++lvIfBuOGEtbMNV5Bt6P/ 2QlG4I2PJFILA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Qypkd3vrKz9rxD; Sat, 8 Jul 2023 14:00:57 +0200 (CEST) In-Reply-To: <83h6qed8kw.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, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=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:307613 Archived-At: Eli Zaretskii writes: >> > That is already a problem, as long as we are talking about leaving >> > most of Emacs application code intact. How do you ensure only the >> > main thread can process input and display? A non-main thread can >> > easily call some function which prompts the user, e.g., with >> > yes-or-no-p, or force redisplay with sit-for, and what do you do when >> > that happens? >> >> To signal an error. > > Great! that means in practice no existing Lisp program could ever run > in a non-main thread. It isn't a very practical solution. > > Besides, non-main threads do sometimes legitimately need to prompt > the user. It is not a programmer's error when they do. As an alternative async threads can be temporarily changed to cooperative in such scenario. They will already have to wait synchronously when consing new objects anyway. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at