emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: bug in expansion of variables in babel Perl
Date: Sun, 24 Feb 2013 13:17:32 +0100	[thread overview]
Message-ID: <87txp1zz1f.fsf@Rainer.invalid> (raw)
In-Reply-To: 87ppzq138q.fsf@mn.cs.uvic.ca

D M German writes:
> I see two ways to solve this. The first is simply to replace the output
> format of the variable from "%S" to "'%s'" (use quotes ').

I think that's the right thing to do.  There shouldn't be anything in
the table that needs to be interpolated by Perl while the variable is
defined.

> +    (format "'%s'" var)))

A slightly more perlish way would be to use
       (format "q(%s)" var)))

> Debugging perl is very cumbersome in org-mode. It would be nice to have
> a feature to export the source to a file. This is because the variable
> expansion needs to be done before the code can be used (hence simply cut
> and paste does not work, nor shell-command-on-region)

The other languages have the same problem, maybe there should be a
general option to mirror the commands into a source block in the org
file or to make the buffer with the program to be eval'ed stick around.

Eric, WDYT?  Also, I'm not really sure why we need all the complexity of
shell-command-on-region when it looks like we should be able to
call-process-region ourselves.  Modifying Babel to run (non-session and
perhaps optionally) from files instead of buffers seems to be a more
wide-reaching operation.

> As we are into it, I found this declaration to be very useful. 
[…]

I think this is better done by altering org-babel-perl-command to
include "-Mstrict".  If you put the helper functions into a module in
@INC or tell Perl where to find them, then you can add "-Mmyhelper" as
well.  Here's a wrapper to match:

(defvar org-babel-perl-wrapper-method
  "{
  my @r = eval( q(%s) );
  open my $BO, qq(>%s));
  print $BO join($\\, @r), $\\ ;
}")

For your problem with :results output blocks, I think it would be
possible to wrap them (a bit differently) also, but the "helper module"
above would also solve this problem, so let's see what Eric says since I
don't know if another language has already set a precedent of wrapping
these commands too.

>
> Finally, if interested, i can write a couple of examples for Perl that
> could help people who want to use it. 

Also a few tests would be highly welcome.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

  parent reply	other threads:[~2013-02-24 12:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-24  9:16 bug in expansion of variables in babel Perl D M German
2013-02-24  9:45 ` dmg
2013-02-24 10:23   ` D M German
2013-02-24 13:08     ` Achim Gratz
2013-02-24 18:20       ` D M German
2013-02-24 12:17 ` Achim Gratz [this message]
2013-02-24 16:52   ` Eric Schulte
2013-02-24 17:15     ` Achim Gratz
2013-02-24 18:03     ` Achim Gratz
2013-02-25  9:44       ` D M German
2013-02-24 17:05 ` [PATCH] " Achim Gratz
2013-02-25  9:42   ` D M German
2013-02-25 12:48     ` Achim Gratz
2013-02-25 21:54       ` D M German
2013-02-26 11:13         ` Achim Gratz
2013-03-02 22:01   ` Achim Gratz

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=87txp1zz1f.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    /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).