From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: allow multiline #+BIND Date: Thu, 31 Jul 2014 11:36:32 +0200 Message-ID: <8761idkgyn.fsf@nicolasgoaziou.fr> References: <31633.8990153328$1406720103@news.gmane.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39930) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XCmmD-0001pQ-8I for emacs-orgmode@gnu.org; Thu, 31 Jul 2014 05:36:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XCmm6-00044F-Fi for emacs-orgmode@gnu.org; Thu, 31 Jul 2014 05:35:57 -0400 Received: from relay5-d.mail.gandi.net ([2001:4b98:c:538::197]:42529) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XCmm6-000444-6T for emacs-orgmode@gnu.org; Thu, 31 Jul 2014 05:35:50 -0400 In-Reply-To: <31633.8990153328$1406720103@news.gmane.org> (Vladimir Alexiev's message of "Wed, 30 Jul 2014 14:33:47 +0300") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: vladimir.alexiev@ontotext.com Cc: emacs-orgmode@gnu.org Hello, "Vladimir Alexiev" writes: > It would be nice to allow multiline BINDs. I'd much rather write this > than put it all on one line: This was suggested already for other keywords, e.g., MACRO. and CALL (http://permalink.gmane.org/gmane.emacs.orgmode/69326). > The usual continuation syntax of backslash before the EOL can be used. This can be an option. What would be needed is an unambiguous syntax (e.g., what happens to lines ending with a backslash, without meaning a continuation?). Bonus points if it is elegant, too. > Or else, a new keyword #+BIND1: for each continuation line. No, BIND1 is also a valid keyword name. This could introduce a clash. > The function to fix is ox.el::org-export--list-bound-variables No, keyword parsing happens in `org-element-keyword-parser' and `org-element-babel-call-parser' for the special #+CALL: keyword. Regards, -- Nicolas Goaziou