From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id eOfeFkXuCWRHsQAASxT56A (envelope-from ) for ; Thu, 09 Mar 2023 15:33:41 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id OAVDFkXuCWTRfgAAauVa8A (envelope-from ) for ; Thu, 09 Mar 2023 15:33:41 +0100 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 09164270B4 for ; Thu, 9 Mar 2023 15:33:40 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1paHK1-0003YA-Ta; Thu, 09 Mar 2023 09:32:45 -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 1paHK0-0003Y1-9G for emacs-orgmode@gnu.org; Thu, 09 Mar 2023 09:32:44 -0500 Received: from mout-p-202.mailbox.org ([2001:67c:2050:0:465::202]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_CHACHA20_POLY1305:256) (Exim 4.90_1) (envelope-from ) id 1paHJy-0006ef-39; Thu, 09 Mar 2023 09:32:43 -0500 Received: from smtp202.mailbox.org (smtp202.mailbox.org [10.196.197.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-202.mailbox.org (Postfix) with ESMTPS id 4PXWqB1LfCz9slN; Thu, 9 Mar 2023 15:32:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kraus.my; s=MBO0001; t=1678372342; h=from:from: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; bh=zIGUMfbHYy2TF1antYujoIZ3KmqUXad5jPOl6Xk/cRI=; b=g60yoOVBL+BkZbyBXJWNbpsxS0zoKUZTZeBRKTeM+ah9sMml2G4LVUYb2YhIdFIZt5iLMU H3WTBIn/r5RekajJ0yWgiYcZhAGMhSyUd4qaQbv4wbBNnlGhZyd0JlNUwgZYW83Fzc5v/m QN8dBamgmr6AkntMVf3c6ur93UlhIxG01zu/xcOngYrmKV3WG9FTKKTWvOZ4z1jdgSZXnM E9RzWswpTC2mC5cTBUpTV6swiMN5h62W8oA6ocDreHHqRzkqr+0m3yG3BQOWmyCSaR08Ua 8NBoXjeUij7yZWyoW1gmFfM4rgdtQu0rYdVE/d4+Vft8r+EV4XCw+yZ4L08qdw== References: <9eab60bc-9b82-e037-d63b-3d879573ae32@posteo.de> <87v8jceihi.fsf@localhost> <7fc63848-d6d3-80e0-ae78-00967990813d@posteo.de> <64079614.170a0220.5a0d3.0a23@mx.google.com> <97ee254e-72d2-2bdf-e026-78bde076f1f9@posteo.de> <6408e424.5d0a0220.8862a.2a62@mx.google.com> <87pm9ioyrg.fsf@localhost> From: Daniel Kraus To: Ihor Radchenko Cc: Zelphir Kaltstahl , Bastien , Bruno Barbier , emacs-orgmode@gnu.org Subject: Re: org-babel guile source block bug in handling multiple values Date: Thu, 09 Mar 2023 15:21:38 +0100 In-reply-to: <87pm9ioyrg.fsf@localhost> Message-ID: <87r0ty572s.fsf@kraus.my> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: none client-ip=2001:67c:2050:0:465::202; envelope-from=daniel@kraus.my; helo=mout-p-202.mailbox.org X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 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_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001 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 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1678372421; 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=zIGUMfbHYy2TF1antYujoIZ3KmqUXad5jPOl6Xk/cRI=; b=Z5U2ojuUD65pnJVudiTrYCiFl4qZrYYK0FUr87JageCAf1Bn4GVyu7JkNwzexs+WmgOpMF ZJalkM8Xyp3VBZ+7vXsXr8AO/t1tlsyebtBdDnFpJ9fr/QLPwW9fpiDNw3z81ZSU8cDO7w WYoAhHxB1pyGnVETEC1Ov0ZGbul80LsQnKlRGWYtwwkXLiQQQoorA64VIhOrfu/tWB1k8k hA5zEV977D3duj6NolNRC00QZokNDMrMbJSA2BnEI83egWx3I85h9G5k5M/9CaRJHHgXGD G5Dzx7knnLMKdJMCrdTCz+ba8MF18uubtRZFNkr0EkaHdaoM+NNI7mw32n6awg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=kraus.my header.s=MBO0001 header.b=g60yoOVB; 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=none ARC-Seal: i=1; s=key1; d=yhetil.org; t=1678372421; a=rsa-sha256; cv=none; b=u64IuGfJ7JVgxAAyFSbipzcbFAPRn7xU8Vo2/f6TODYI6QVFAo8WWR44hZi4wmLeEnCiss eyYQkExB19VHdzmQWL2vW7+9dQgoq4w/ULQtDLff4DcfLKo+PouqtBEoZXa52DPYoIb43i 9PJBhjVfZ0G4NpmYeo3suX2mlpxJN6gdEp7/DvwVR4dE32xqTDGv8EJBssEtp1t6ndwRqZ wl7by5ybIJtjsuAalNv50pou7WxFfCYr7PBjeb3mqRFBoysNCf0DiNQi98MnooVsD1kqGf fcsWBF8Wz2NIDBG4VBZ/z3miK8M9nQcluNYecj0wturp0FQyTSJ6fwiiy36o3A== Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=kraus.my header.s=MBO0001 header.b=g60yoOVB; 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=none X-Migadu-Spam-Score: -0.80 X-Spam-Score: -0.80 X-Migadu-Queue-Id: 09164270B4 X-Migadu-Scanner: scn1.migadu.com X-TUID: JBMMQIRJTz3h Ihor Radchenko writes: > Zelphir Kaltstahl writes: >> (q1) What is a rationale, if any, behind the let-wrapping? > > It makes sense in ob-emacs-lisp to not litter global Emacs state. > In other ob-* lisp backends, I am not sure. > I am CCing Daniel, the maintainer of ob-clojure (we have no active > maintainer for ob-scheme now). Maybe, Daniel has some useful insight. No, unfortunately I don't have any more insights than already discussed. I think wrapping the vars in let just seems natural for lisps. If I could freely choose if a :var declaration in one source block should create a global variable for all other blocks in this session, I would say making it only available in the defining source block is more natural (i.e. use let instead of def). But given that apparently almost all other babel languages define a global var, I'll just make the same change in ob-clojure?! Cheers, Daniel