emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Vladimir Alexiev <vladimir@sirma.bg>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: org-babel-read should have option NOT to interpret as	elisp
Date: Sun, 27 Feb 2011 16:44:45 -0700	[thread overview]
Message-ID: <87hbbpyrde.fsf@gmail.com> (raw)
In-Reply-To: <loom.20110228T002523-131@post.gmane.org> (Vladimir Alexiev's message of "Sun, 27 Feb 2011 23:28:45 +0000 (UTC)")

Vladimir Alexiev <vladimir@sirma.bg> writes:

>> would be onerous to have to wrap every cell
>> of a table in double quotes...
>
> I tried doing this as a workaround, but it is not 
> since the quotes are passed to perl, and that's not what I want
>
>> it would be a breaking change for
>> anyone who is currently relying on the ability
>
> Right, that's why I think it should be an option.
> The default could stay as is, but should be documented.
>

What syntax would you suggest to indicate that a variable is to be
passed without the possibility of elisp evaluation.  I agree making this
behavior optional would be ideal, but I couldn't think of an intuitive
syntax.

Cheers -- Eric

  reply	other threads:[~2011-02-27 23:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-27 14:14 org-babel-read should have option NOT to interpret as elisp Vladimir Alexiev
2011-02-27 15:51 ` Eric Schulte
2011-02-27 23:28   ` Vladimir Alexiev
2011-02-27 23:44     ` Eric Schulte [this message]
2011-02-28  0:30       ` Vladimir Alexiev
2011-03-01  3:11         ` Eric Schulte
2011-03-01 12:19           ` Vladimir Alexiev
2011-03-01 16:58             ` Eric Schulte
2011-03-02  7:20               ` Vladimir Alexiev
2011-03-02 14:56                 ` Eric Schulte
2011-02-28 10:07   ` Sébastien Vauban
2011-03-01  3:10     ` Eric Schulte

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=87hbbpyrde.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=vladimir@sirma.bg \
    /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).