title: org-mode emacs won't export
body: <p>I admit I'm a total emacs and org-mode newbie.
  It worked great for me, but suddenly I'm having the following problem.</p>
  
  <p>Say I open a file test.org with emacs</p>
  
  <p>$ emacs test.org</p>
  
  <p>The file contains:</p>
  
  <pre><code>* one
  * two
  ** a
  ** b
  </code></pre>
  
  <p>When I try to export with 
  C-x C-e 
  I get the following error message:</p>
  
  <pre><code>Debugger entered--Lisp error: (void-variable b)
    eval(b nil)
    eval-last-sexp-1(nil)
    eval-last-sexp(nil)
    call-interactively(eval-last-sexp nil nil)
  </code></pre>
  
  <p>I just found out about org-mode and was immediately ecstatic about it.
  Within minutes I could refactor my plain text notes for org-mode, including math formulas and export them to latex and from there pdf. I used C-x C-e o as explained here: <a href="http://orgmode.org/manual/LaTeX_002fPDF-export-commands.html" rel="nofollow">http://orgmode.org/manual/LaTeX_002fPDF-export-commands.html</a></p>
  
  <p>This worked great on both the GNU Emacs 23.3.1 that I have on my Mac OS X Terminal as well as with the newest Emacs release 24.1 which I had installed as a standalone .app </p>
  
  <p>Unfortunately this didn't last very long and I got the error message described above, even for the most simple org files. What strikes me, that both installations of emacs started having this problem at the same time. I even deleted my, slightly modified, .emacs file in the home directory but that didn't help either.</p>
  
  <p>It seems like emacs always fails wie evaluating the last line. If I delete it</p>
  
  <pre><code>* one
  * two
  ** a
  </code></pre>
  
  <p>The error message is:</p>
  
  <pre><code>Debugger entered--Lisp error: (void-variable a)
    eval(a)
    eval-last-sexp-1(nil)
    eval-last-sexp(nil)
    call-interactively(eval-last-sexp nil nil)
  </code></pre>
  
  <p>Any help is very much appreciated! I very much like org-mode and would love to learn el. However, at the moment I don't even know how to write more than two lines of LISP. Googling for this error message leaded to descriptions of problems that seemed to be totally unrelated.</p>