From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: change in babel argument processing? Date: Mon, 08 May 2017 11:27:16 +0200 Message-ID: <87a86n7l6z.fsf@nicolasgoaziou.fr> References: <87tw4vspdm.fsf@t3610> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54789) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d7ewt-0006bO-Ce for emacs-orgmode@gnu.org; Mon, 08 May 2017 05:27:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d7ewq-0000MK-87 for emacs-orgmode@gnu.org; Mon, 08 May 2017 05:27:23 -0400 Received: from relay7-d.mail.gandi.net ([217.70.183.200]:53036) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1d7ewq-0000M7-22 for emacs-orgmode@gnu.org; Mon, 08 May 2017 05:27:20 -0400 Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) by relay7-d.mail.gandi.net (Postfix) with ESMTPS id 061D5119B for ; Mon, 8 May 2017 11:27:16 +0200 (CEST) Received: from saiph.selenimh (00004301000000000000074b.ipv6.commingeshautdebit.fr [IPv6:2a03:a0a0:0:4301::74b]) (Authenticated sender: mail@nicolasgoaziou.fr) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id CCD4EA80D7 for ; Mon, 8 May 2017 11:27:16 +0200 (CEST) Received: from ngz by saiph.selenimh with local (Exim 4.89) (envelope-from ) id 1d7ewm-00054z-Ct for emacs-orgmode@gnu.org; Mon, 08 May 2017 11:27:16 +0200 In-Reply-To: <87tw4vspdm.fsf@t3610> (Eric S. Fraga's message of "Mon, 08 May 2017 09:51:17 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Hello, Eric S Fraga writes: > Some of my ledger babel calls have stopped working. I have tracked it > down to a change in how backslashes are treated. Formerly, I had > "...\n..." which was interpreted correctly but now require to escape the > backslash "...\\n...", as in the attached example. > > I'm posting this as much as a heads up for others as anything else. I > did not see any mention of this in the list or the change log but could > have obviously missed it easily (apologies if so). It is an unexpected consequence of 500abcd7fbe24abc887300faec2058905a13fa33 in which I lazily use `read' to parse string values. I fixed it in maint, could you confirm it? Thank you. Regards, -- Nicolas Goaziou