From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id cJvjFcAc2mW5WwEAqHPOHw:P1 (envelope-from ) for ; Sat, 24 Feb 2024 17:43:44 +0100 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id cJvjFcAc2mW5WwEAqHPOHw (envelope-from ) for ; Sat, 24 Feb 2024 17:43:44 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=g9BQLm7d; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1708793024; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=/Gaj/6YGcYXe0b5Oo4/24eOax7uJmIx19usYlqxwEoE=; b=er3HpmQJ5ORMLJ90VeOVGSQS+w8L618uVMpkyWEFSXRy2mK9vIbAFPgqkK159tJWR7rKfs i9gVhBPJZyUrg2xmau3O9AxIt4qcTJSVaFqygqzl9c6VFawe52YEJA5dEeiLyakJll5naC V6u9C3dNVsq0qtVbLEOb0gewuAqPSUuJi8iJuEX/1oH6tXpjEhavpyot+phnmT/MQctSC/ Mm938+lPCb39Sb9iSVTMuwS/PsflL2ZiBPzCMtcv4Xkab1G/CXaAkTcLsQw5TVXITTVvXy MqVdbklEVSBMXba3gcs0pUPpPowVlKs7ZUz+YxfkRCUQ4zd3iLbKz0wEhq7v/Q== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=g9BQLm7d; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1708793024; a=rsa-sha256; cv=none; b=Eg+YmZwCAwjUWUx2mRi87jefnbTq6t39LN5EanBXp1hSKJAxY+3EnS9PKzLaGcouD4Oiv1 p2nERHMvvQPMPVAFH5B9aJOWmkks96KS4Npu50zu9Wu+qkZu25t8si7ADCbHCq2CZqpbKx jxZHUUqWhxsS6MFDCxYLCm2ZtHP7KRdny/WASGRhauyUlLUdw6g+02fp6b6HlYCFM8aRlL FOZX19zeJ9lUZHiKMSEq/P/Zlg76Ti17dcKUZKDifVbbhTk2JRWDgOonmVse3UDMJAhCEO kJlHuBl1sKmHgEBNj8+XG+3WBa7XPbwQco+tUA8xmEAtj7CrX5+NnrIYD74AAA== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 0F51A2642F for ; Sat, 24 Feb 2024 17:43:44 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rdv77-0005tA-OZ; Sat, 24 Feb 2024 11:43:01 -0500 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 1rdv76-0005sG-Hl for emacs-orgmode@gnu.org; Sat, 24 Feb 2024 11:43:00 -0500 Received: from mail-wm1-x32a.google.com ([2a00:1450:4864:20::32a]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rdv74-0007WS-N5 for emacs-orgmode@gnu.org; Sat, 24 Feb 2024 11:43:00 -0500 Received: by mail-wm1-x32a.google.com with SMTP id 5b1f17b1804b1-4129e978a5fso2473785e9.0 for ; Sat, 24 Feb 2024 08:42:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708792976; x=1709397776; darn=gnu.org; h=mime-version:date:references:in-reply-to:subject:cc:to:from :message-id:from:to:cc:subject:date:message-id:reply-to; bh=/Gaj/6YGcYXe0b5Oo4/24eOax7uJmIx19usYlqxwEoE=; b=g9BQLm7dXKAJ3TO6/hWNuo5cSdp8f/s6paVuIP5WYXE+5Y/kwO/tPbyru1DKzF05bL fcyfP4+AFmPcmluTlhVt+vyx1INPyY8DwQEf/twig53U1o7i++6hffob3Nx+WEP9IolK PdQioLZfwDJtXgz1WjnfX0WhTQMg8Eyrpi6n60hRfA8/WPboSfU84GghttbWn5yzMhDa KLA2Nhny9z6i2PdAcSQChXM9i+AuJtPypbhx7YORqPRNtyhS+PasxDarLottQ5Jlc4CV B0OnI1UHEzYRPVxfilsVgVAtxlqzavQpJ+E3pZgr7lBkcFFg/7wATok+BnjlyB1SUxPI 4Gqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708792976; x=1709397776; h=mime-version:date:references:in-reply-to:subject:cc:to:from :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/Gaj/6YGcYXe0b5Oo4/24eOax7uJmIx19usYlqxwEoE=; b=KzY3gZQxyDeCdzgaOS7RJau5Egglno03i7VpkohB6yQVJ2Vt7aO/slaecEPUrDl9A+ tMZslr7aCr0IO6vVx6+X6DIyV4O+IFXoSaKT/mhljMl9Ik8jFkp4pehBBkP/wBBu/MLl cbSdSd7I+IVm837W8vOnktluCHEDgxYOzkOTyKc76FJmXAo2n65xRy+s9Acy2Xl/ROaZ XGCXh0UWJ/Q1aQvUt3g7IEnntxxZznMV9RoZamqqNkOS0RwdFSZpDq1LgdJT6YyFTK0i mx6lQvkWXoa+Q8i3zLTrKqAbk95Sic0i2AiuVqHM2WvbBtvnkqmx/d+uotNnJ0NC8aRk pn0g== X-Forwarded-Encrypted: i=1; AJvYcCUvSbHMK/nIPfPKs8IbcAxylGtvKeSvCeCUXZhE87j1KEX+9JM7mGiHgy9PnYh3PqLktS8tV7hyEaAgrB8LSMudfjp4HU0= X-Gm-Message-State: AOJu0Yx4WqwsnMaKMqju0E+DYdOdTDUrRyCkItt2qHt3V870an/RHyrb MFDRRIe6/tcyaV5kDGb2Dp3Z6Puf6EuRI6BB6PgHVY1TTbm/LnHC X-Google-Smtp-Source: AGHT+IEdxS6tKEIScKPlrO87Q8ViXc7vzGLN85kaJnnso4ZJt2SSQZenjnA7NHLaB7KbUetshXTReA== X-Received: by 2002:a5d:6150:0:b0:33d:c5c7:4182 with SMTP id y16-20020a5d6150000000b0033dc5c74182mr437625wrt.7.1708792976215; Sat, 24 Feb 2024 08:42:56 -0800 (PST) Received: from keynux ([2a01:e0a:505:3460:1c18:688d:ece4:372e]) by smtp.gmail.com with ESMTPSA id bk14-20020a0560001d8e00b0033cdbe335bcsm2692712wrb.71.2024.02.24.08.42.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 24 Feb 2024 08:42:55 -0800 (PST) Message-ID: <65da1c8f.050a0220.8b19a.58e5@mx.google.com> Received: by keynux (sSMTP sendmail emulation); Sat, 24 Feb 2024 17:42:54 +0100 From: Bruno Barbier To: Ihor Radchenko Cc: Matt , Jack Kamm , emacs-orgmode Subject: Re: Asynchronous blocks for everything (was Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/build/org/)]) In-Reply-To: <878r3axecb.fsf@localhost> References: <87o7d0mm54.fsf@localhost> <65bbb108.050a0220.b60fd.6790@mx.google.com> <87jznm8hcu.fsf@gmail.com> <875xz42rp9.fsf@localhost> <874jen8zec.fsf@gmail.com> <87o7cv9e80.fsf@localhost> <65c2875f.050a0220.caf6d.8291@mx.google.com> <18dae5cab1d.bf1c7563863897.4896289306902277373@excalamus.com> <65cfa0d8.050a0220.cb569.ce34@mx.google.com> <87frxohlgo.fsf@localhost> <65d61ec7.050a0220.999f7.a39b@mx.google.com> <87jzmvjs7m.fsf@localhost> <65d89ca9.050a0220.757c8.6fdd@mx.google.com> <878r3axecb.fsf@localhost> Date: Sat, 24 Feb 2024 17:42:54 +0100 MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2a00:1450:4864:20::32a; envelope-from=brubar.cs@gmail.com; helo=mail-wm1-x32a.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx12.migadu.com X-Migadu-Spam-Score: -8.00 X-Spam-Score: -8.00 X-Migadu-Queue-Id: 0F51A2642F X-TUID: nmOmneDvNWxv Ihor Radchenko writes: > Bruno Barbier writes: > >>> May you please clarify if adding the new code block parameter that >>> defines custom execute function is something you want to add to Org mode >>> or just a helper code to demo you main patch? >> >> Yes. (I thought about adding it in a separate request; but that would be >> simpler to include it.) > > I have doubts about how useful such parameter would be for _users_. It > is certainly useful for developers of new babel backends, but I do not > see how users will use it. > > I'd prefer to discuss this in a separate thread. Sure. I'll keep it for an other thread. >>> Error buffer does not necessarily appear on failure. When the code leads >>> to process writing to stderr, we also display error buffer. Even if the >>> process exits with 0 code. >> >> Got it. The current design adds the popup on failure; I should make it >> more flexible to allow to configure a popup on success too. > > By popup, do you mean an overlay where clicking on it will raise the > usual `org-babel-eval-error-notify' buffer? > If yes, what happens if a user executes a code block, it fails, and the > user executes it again without looking at the error? (Second execution > may be triggered from a different place, indirectly, via noweb ref or > similar). Current behavior is to remove the error, and, then re-execute: the previous errors are gone. My guess is that this could be improve later, without breaking the API. >> But if the execution fails, I guess I'll need to provide some feedbacks >> anyway, but I don't know yet how (asynchronous popups are not an option, >> modifying the file neither). > > We need something more than just an overlay. Maybe some kind of babel > execute history (in tabulated-list-mode buffer), keeping information > about execution stats and stderr data. > > We may provide a mode-line or fringe indicator that will warn user if > something went wrong with recent executions. Something akin compile-mode > mode line indicator listing errors and warnings during compilation. I was thinking about using a fringe indicator, for warnings on success (as I'm removing all overlays on success). Keeping a buffer of all asynchronous executions looks like a good idea. I'll think about it. > (Handling asynchronous messages is actually a complex topic. It has been > previously discussed on emacs-devel as well. See > ) I'll look at this. Thanks! I'll publish a branch soon; it will be a major rewrite of my current proposal. It should be less confusing and, I hope, address some of your comments. Thanks again for your questions and feedbacks, Bruno > > -- > Ihor Radchenko // yantar92, > Org mode contributor, > Learn more about Org mode at . > Support Org development at , > or support my work at