From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id wDfWDkmlA1/QPQAA0tVLHw (envelope-from ) for ; Mon, 06 Jul 2020 22:27:21 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id zMjMCkmlA19gEgAAB5/wlQ (envelope-from ) for ; Mon, 06 Jul 2020 22:27:21 +0000 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 7C1CE9400B1 for ; Mon, 6 Jul 2020 22:27:20 +0000 (UTC) Received: from localhost ([::1]:33120 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jsZa1-0007jv-Um for larch@yhetil.org; Mon, 06 Jul 2020 18:27:17 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:43990) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jsZZg-0007jn-Dg for emacs-orgmode@gnu.org; Mon, 06 Jul 2020 18:26:56 -0400 Received: from mail-ed1-x543.google.com ([2a00:1450:4864:20::543]:33217) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jsZZe-0002w5-Uh for emacs-orgmode@gnu.org; Mon, 06 Jul 2020 18:26:56 -0400 Received: by mail-ed1-x543.google.com with SMTP id h28so36682535edz.0 for ; Mon, 06 Jul 2020 15:26:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=kq0TzWHsDCqQw4PhEdZncm4ZZB+CMfZLadNBGuCSdVQ=; b=Op1HjjB6FoNhFSrDeUvheu+VEWIpt6l0cjCPpOAtijvPKsS7+539LpcB9m+45hJleJ guJK5KDBid02llqxG/F4Y71vQlV/ozXSiraNpXqbLFEC4bUgyiNGKTZsvSTHUPWTReNW rQqY2DMO3DtznKLsxpKHB2ahOmtLlyANYnTA2cM+w65zwvJ9BjhcD28AjppGuxeQzv4m yrGqpQyOYu/u5iF93B5vZOQ2/InO+6U8/sGoUDUl+hzH9M5ZWVFdiHgquw1vt48iH5NQ KLA0cBkhRZ8+cnJmALxaG0NaIYsI4zs5TSNVDOST+h2e0zbXNua6cs++XDNwQsGeI9a5 U+0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=kq0TzWHsDCqQw4PhEdZncm4ZZB+CMfZLadNBGuCSdVQ=; b=LZtrlsI7H6V7niLalhYcV9jK9fCYRvHfuJOlGvZYzZLbM7B+3UDP6JrJVFPAbpBQxS yKpfaScuVk7rytJyoDPjKlYWqwkj3f+13yVM9ayJSX7F3VXIgnhifT5dXOnXQl0Bp23/ dtATG316UoDV31BXKKaGZ+qyyVnl/03Nai85dTgKev5jI0h819q7q+njxMvw0Qw8KUXf b4oreuRaj59hIVVj2BLGjrQL/YAHzFiCUBL6YZ9/dHFuJ8zVt2nmGsU9ZhUWipzhMcIJ gtb0nJVSG/WvgSUA2pMjVvWkjziDidZur6oA2IcmoHyEMax9Mq9TiBY0ZL1huMFz/A3v y1Dg== X-Gm-Message-State: AOAM530GKYBjn0sFtib3K5dzV5A5srpAAgJKCdKqsgiO7oKvTiYEchn2 r3kjuHiWad1mGQX0Tl2gqrT47UGSOPpfDQ== X-Google-Smtp-Source: ABdhPJwPt/3DjndmT5Az5Y2xpCcGp9chBFh6cUiiO9xZynysvo1qaXxs3Mj2ptL2KE9hYOs6wAesbA== X-Received: by 2002:aa7:d043:: with SMTP id n3mr60503179edo.102.1594074413484; Mon, 06 Jul 2020 15:26:53 -0700 (PDT) Received: from localhost ([31.220.2.134]) by smtp.googlemail.com with ESMTPSA id u19sm27400578edd.62.2020.07.06.15.26.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Jul 2020 15:26:52 -0700 (PDT) From: akater To: numbchild@gmail.com Subject: Re: (almost a patch) Receiving more output from a Common Lisp evaluation in Org buffer In-Reply-To: <87zh9wg8yt.fsf@gmail.com> References: <87mu7lzhr8.fsf@gmail.com> <87zh9wg8yt.fsf@gmail.com> Date: Mon, 06 Jul 2020 22:17:27 +0000 Message-ID: <87tuykuw3s.fsf@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Received-SPF: pass client-ip=2a00:1450:4864:20::543; envelope-from=nuclearspace@gmail.com; helo=mail-ed1-x543.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=Op1HjjB6; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: 0.19 X-TUID: kmKGQDZcF+sL --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable stardiviner writes: > I have some considering. Multi-block return might will cause other option= s hard > to handle the result block. For example ~:cache~, ~:results replace~, and= use result > as source block input data. WDYT? Probably. I'm not a user of either :cache or :results replace but multi-block return, if implemented, will likely require some non-trivial work to be incorporated smoothly. Returning just a single block by default will keep it safe for general users. But I do find it suspicious when some output is produced and yet not submitted into the buffer where evaluation results are supposed to go. And Org seems to be able to handle this very neatly. >> while simply hiding empty blocks, if any, for convenience. >> >> Note that currently, when =E2=80=9Coutput=E2=80=9D is specified, =E2=80= =9Cvalues=E2=80=9D is simply >> lost, and vice versa. Implementing multi-block results would fix this >> shortcoming too. >> >> However, I did not try to implement this yet. >> >> * Conclusion >> How do we sync with SLIME if you're OK with this? How do we treat the >> case of vcs Org + stable SLIME? > > Might on Org Mode side, add an function to detect SLIME output, or SLIME = version > to make sure ~:results trace~ is usable. If not, warn user to update SLIM= E. WDYT? For now, I just delayed activation of the feature in Org until a certain future SLIME version. In my SLIME patch, it's handled more subtly, using supplied-p optional argument, a check that can be dropped once Org 9.3 becomes unsupported. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJfA6L8AAoJELK+sWGx7H9ER7UQAIzWAQ8EsADgrEIAfJgSb+ff V9KZXmFE7E8KfN1Urw0OaOCicKlJFKBcbm+fSG6dP3Vw0WFf4Zw4GudTNNp60LrW daqoGuCRDCksg1WrXTkY38UxTz90jxtHHcp6M11kTksEhPczx5mNDA7GPPq2/LyR +tG/v8Ng8X7RsjvrlOl1c9T3iaRLOiyVD48kMTHn0AlYtycBeDOPrsrr/V/4ugti fA6bYVr/Dowutf/tr5wqR4GnktNtd7KoSJrudIX02xnIqKgDviNPKTj6+RAvbdsa f/LC9/VMdzXNPbUrk9U+7am2NNN9p3VnRk9klUTQcx5/M8sSx/CH/omtbGrMvAF/ 8CBKtS8TiSmg7pgUaFZb1KhQ38+xAVhDZJVsDP9QyA7DU/resSPPm8F1Rk+Llytl +/Bxy5wrJ4RdSZby0uvPuKJvRUVM04Ol8/vTKSOWQeyuEy3qtiYhrXbqQsxlnyLG fJCDvtf5gF6IVuBuqh1NbBE/dRLEINyO4wM8E3YPJFBvusc8gQkiLCXs5C5aiU4P iMZ8zdvBuiDiXRidGhrodCLiL5j5mu95w5O9sQEROwfo1fHSHUs8GGWS/5kTJq0R f1mfj3bUy+xSMa0/KtEgsQZ1z0f2u+DYnt2gIlzN5UA/eUMZHCqgiHfq2wO6Ol8d DKz2C+HH0AnrQ7BiYu0Y =0Y9W -----END PGP SIGNATURE----- --=-=-=--