From: "Eric Schulte" <schulte.eric@gmail.com>
To: Chris Malone <chris.m.malone@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Two questions about using a =#+begin_src emacs-lisp= block
Date: Tue, 22 Feb 2011 11:06:00 -0700 [thread overview]
Message-ID: <87d3mkc5br.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTikGF4gxNPnSpTUW+oXbQxqR565x+LW-XccJ+Fsy@mail.gmail.com> (Chris Malone's message of "Tue, 22 Feb 2011 11:57:26 -0500")
Chris Malone <chris.m.malone@gmail.com> writes:
> Ok, this is still perplexing me, as I have a new version from git and I
> still get the error. The following is complete list (sorry for the long
> email!) of what I have done:
>
> * Get a fresh copy of =org-mode= from git and byte-compile:
>
> #+begin_src: sh
> cd ~/install/org-mode
> mkdir new_git_clone
> cd new_git_clone
> git clone git://orgmode.org/org-mode.git
> cd org-mode; make &> make.out
> ln -s ~/install/org-mode/new_git_clone/org-mode ~/install/org-mode/current
> #+end_src
>
if you are worried that you don't have the correct version of Org-mode
installed you can check the output of the `org-version' function. Mine
reads
"Org-mode version 7.4 (release_7.4.510.g1e35)"
>
> During the =make= process, I noticed quite a few warnings. An example is
> below (for a complete copy of =make.out=, see
> http://astro.sunysb.edu/cmalone/nolink/make.out
[...]
> Are such warnings normal?
>
yes, these are normal compiler warnings which are generally cleaned up
before releases but shouldn't have any negative impact on the behavior
of Org-mode
>
> * Make sure my =.emacs= file is pointing to the correct location
> Here is a copy of the =org-mode=-relevant sections of my =.emacs= file:
>
[...]
>
> * Attempt an export of the =org-mode= file found here:
> http://astro.sunysb.edu/cmalone/nolink/python_class_lstings.org
>
One thing to note here, is that for your emacs-lisp block to work on
export, you need to change this
#+begin_src emacs-lisp :exports both
(buffer-file-name)
#+end_src
to this
#+begin_src emacs-lisp :var file-name=(buffer-file-name) :exports both
file-name
#+end_src
because only header arguments are guaranteed to be evaluated in the
original org-mode buffer during export.
That said I was able to export your example file (without the change
above) to html. When exporting to latex I ran into an issue, the
problem here is that the LaTeX exporter *requires* at least one
headline. It explicitly export the pre-first-headline and
post-first-headline portions of the Org-mode buffer separately. When
there is no headline, and the buffer contains code blocks, then they are
exported *twice*, which causes the error you mentioned, because after
the first pass of the code-block export, the results in the file are not
valid for another pass of the exporter.
If you place a "* " before the "Let's start this..." line, then the
errors should disappear.
Hope this helps.
Best -- Eric
next prev parent reply other threads:[~2011-02-22 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 22:08 Two questions about using a =#+begin_src emacs-lisp= block Chris Malone
2011-02-21 17:17 ` Eric Schulte
2011-02-21 18:31 ` Chris Malone
2011-02-21 19:48 ` Eric Schulte
2011-02-22 15:06 ` Chris Malone
2011-02-22 16:54 ` Eric Schulte
2011-02-22 16:57 ` Chris Malone
2011-02-22 18:06 ` Eric Schulte [this message]
2011-02-22 18:23 ` chris.m.malone
2011-02-22 18:45 ` Achim Gratz
2011-02-21 22:19 ` Dan Davison
2011-02-21 22:34 ` 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=87d3mkc5br.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=chris.m.malone@gmail.com \
--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).