Hi,<br><br>First off, my =org-mode= is up-to-date - just did a =git pull &amp;&amp; make clean &amp;&amp; make=.  Needless to say, the following were an issue before then...<br><br>* Question 1:<br>Is there a way to force, upon export, an =emacs-lisp= session to be run within the current buffer?  For instance, the following code<br>
<br>===============================================================<br>#+begin_src emacs-lisp :exports both                                            <br> (buffer-file-name)                                                             <br>
#+end_src <br>===============================================================<br><br>exports to LaTeX as<br><br>===============================================================<br>\begin{verbatim}                                                                <br>
(buffer-file-name)                                                              <br>\end{verbatim}                                                                  <br>                                                                                <br>
                      <br>===============================================================<br><br>In other words, as far as I can tell, the code is passed to the interpreter, which does not know about the current buffer information, and therefore the result of the =emacs-lisp= code is an empty string.  By contrast, if I use =C-c C-c= to evaluate the code block, then I get the proper result printed in the =.org= buffer:<br>
<br>===============================================================<br>#+results:                                                                      <br>: /home/cmalone/org_tests/<a href="http://python_class_lstings.org">python_class_lstings.org</a><br>
===============================================================<br><br>Ultimately, I&#39;d like to, upon export, have a =emacs-lisp= code block that does a regexp search on the file and returns a list of matches, which can then be placed in a =latex= code block.  This sort of action suffers from the same issue as the =(buffer-file-name)= code - in essence this is a minimal (non)working example.<br>
<br>* Question 2:<br>Why does the following code, upon export, ask if I want to evaluate the =emacs-lisp= code *TWICE* and then give a /Invalid read syntax: &quot;#&quot;/ error in the message window?:<br><br>===============================================================<br>
#+begin_src emacs-lisp :exports both                                            <br> (buffer-file-name)                                                             <br>#+end_src                                                                       <br>
                                                                                <br>#+begin_src sh :exports both                                                    <br>  ls -l                                                                         <br>
#+end_src<br>===============================================================<br><br>Note that this works fine as long as the =:exports= tag for the =emacs-lisp= code block is *NOT* =both= or =results=.  Also note that the value of the =:exports= tag on the =sh= code block is irelevant for this error to appear.  Also, it doesn&#39;t have to be this particular combination of =emacs-lisp= and =sh= blocks; for instance it fails with an =emacs-lisp= and a =python= source block.<br>
<br>Is this a bug?<br><br>Chris<br>