Hi Eric<br><br>thanks, after some fiddling I was able to make it work...<br><br>But do I get it right?<br><br>The snippet has to be explicitely named, I can&#39;t tell the hyperlink just to take the next block?<br><br>Before I start trying it, is it theoretically possible to write an on ob-multiline.el which parses the following lines? <br>
<br>I.e. is the current &quot;point&quot; known at execution time?<br><br>Out of curiosity, the manual says<br><br>&gt; The <code>org-babel-load-languages</code> controls which languages are enabled for
evaluation (by default only <code>emacs-lisp</code> is enabled).  <br><br>Is it done out of security reasons? Cause it wouldn&#39;t be a problem to start a  process via elisp and (shell-command ...)<br><br>Next question:<br>
<br>shell-command normally prints the stdout into the minibuffer, but org-hyperlink executions overwrite it with the return code.<br><br>Is this behaviour configurable?<br><br>Thanks for the help<br>  Rolf<br><br>PS: ob-perl.el says<br>
-----<br>(defun org-babel-perl-initiate-session (&amp;optional session params)<br>  &quot;Return nil because sessions are not supported by perl&quot;<br>nil)<br>------<br>What is meant with supporting sessions? IIRC do packages like sepia.el fork a perl process allowing bidirectional communication with emacs. <br>
<br>Or what kind of extra support is neccessary here?<br><br><br>