emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: vladimir.alexiev@ontotext.com
Cc: emacs-orgmode@gnu.org
Subject: Re: allow multiline #+BIND
Date: Thu, 31 Jul 2014 11:36:32 +0200	[thread overview]
Message-ID: <8761idkgyn.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <31633.8990153328$1406720103@news.gmane.org> (Vladimir Alexiev's message of "Wed, 30 Jul 2014 14:33:47 +0300")

Hello,

"Vladimir Alexiev" <vladimir.alexiev@ontotext.com> 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

      parent reply	other threads:[~2014-07-31  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 11:33 allow multiline #+BIND Vladimir Alexiev
2014-07-30 18:10 ` Sebastien Vauban
2014-07-31  9:36 ` Nicolas Goaziou [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8761idkgyn.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=vladimir.alexiev@ontotext.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).