emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Martyn Jago <martyn.jago@btinternet.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] :var assignment no longer tolerant of whitespace
Date: Sun, 20 Nov 2011 09:28:36 -0700	[thread overview]
Message-ID: <87aa7qwwq3.fsf@gmail.com> (raw)
In-Reply-To: m2zkfrc86u.fsf@btinternet.com

Hi Martyn,

Tom mentioned this regression earlier and I treated it as a new
restriction on variable specifications, but if multiple people are
running into this issue I suppose spaces around equals should be
supported.

I have just pushed up a change and a test case ensuring that examples
like yours below will work.

Cheers -- Eric

Martyn Jago <martyn.jago@btinternet.com> writes:

> Martyn Jago <martyn.jago@btinternet.com> writes:
>
> (Fixed typos in heading)
>
> Hi
>
> It used to be the case that you could assign a variable and any
> whitespace would be chomped:
>
>
> #+begin_src emacs-lisp :var a = 1 :var b = 2
>
> (+ a b)
>
> #+end_src
>
>
> However it is now required to remove the whitespace:
>
>
> #+begin_src emacs-lisp :var a=1 :var b=2
>
> (+ a b)
>
> #+end_src
>
>
> I haven't noticed any announcement of a change in terms of whitespace
> use, so I'm mentioning it in case it is actually a regression, or is it
> by design? If the change has been announced, then I apologize in advance
> for the noise.
>
> Best, Martyn
>
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

  reply	other threads:[~2011-11-20 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-20 11:46 [babe] :var assignment no longer of tolerant of whitespace Martyn Jago
2011-11-20 12:03 ` [babel] :var assignment no longer " Martyn Jago
2011-11-20 16:28   ` Eric Schulte [this message]
2011-11-21 11:37     ` Martyn Jago

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=87aa7qwwq3.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=martyn.jago@btinternet.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).