emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Hannon <jm_hannon@yahoo.com>
To: Org-Mode List <emacs-orgmode@gnu.org>
Subject: Problems with Org-Mode export
Date: Fri, 16 Sep 2011 10:50:01 -0700 (PDT)	[thread overview]
Message-ID: <1316195401.36711.YahooMailNeo@web161909.mail.bf1.yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2189 bytes --]

Greetings.  I've been having problems lately in exporting Org-Mode source-code
documents to HTML and/or PDF.

I'm running Org-Mode 7.7 with Emacs 23 on 64-bit linux (Fedora 15).

I've appended a document that exhibits at least some of the problem.  The
problems are similar to the problem described at:


and can *sometimes* be circumvented by executing org-reload.

In the particular example shown below, the HTML export works as expected, but
the PDF export fails with message:

    org-export-latex-preprocess: Wrong type argument: stringp, nil

By the way, everything worked fine in the example until I added the last
source block:

    #+begin_src R



I tried using what I take to be the latest version of Org-Mode:

    Org-mode version 7.7 (release_7.7.290.g65d05)

but that only made things worse.  I tried an HTML export with this version, and
it generated a horrendous-looking message that begins with:

org-babel-R-evaluate: Wrong number of arguments: #[(session body result-type
result-params column-names-p row-names-p) Æ=}...

followed by a bunch of stuff containing enough non-printing characters that
it's hard to reproduce in email, and ending with:

...org-mode/lisp/ob-R.elc" . 9734)], 5

I'd welcome any help/advice that anybody can provide.


-- Mike

########## Sample file that exhibits some export problems

#+TITLE: This is a test

#+AUTHOR: Michael Hannon
#+email: jm_hannon@yahoo.com

#+BABEL: :session *R* :cache yes :results output graphics :exports both :tangle yes

* Getting Started

** Batch Mode

#+begin_src R :exports code

pdf("xh.pdf") # set graphical output file
hist(rnorm(100)) # generate 100 N(0,1) variates and plot their histogram
dev.off() # close the graphical output file


If we put the code above in a file called =z.R=, we can execute the
code from the command line via: =R CMD BATCH z.R=

#+begin_src R
  x <- c(1, 3, 5)

#+begin_src R



#+begin_src R

  q <- c(x,x,8)


#+begin_src R



[-- Attachment #2: Type: text/html, Size: 2687 bytes --]

             reply	other threads:[~2011-09-16 17:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 17:50 Michael Hannon [this message]
2011-09-16 20:04 ` Problems with Org-Mode export Michael Hannon
2011-09-17  4:59 ` David Maus
2011-09-19 21:17   ` Michael Hannon
2011-09-19 23:20     ` [PATCH] Check argument is a string before calling string-match Bernt Hansen
2011-10-04 12:36       ` [Accepted] " Carsten Dominik
2011-09-20 19:31 ` Problems with Org-Mode export Michael Hannon
2011-09-20 20:29   ` Nick Dokos
2011-09-21  1:09     ` Michael Hannon
2011-09-21 14:37       ` Nick Dokos
2011-09-21 19:10         ` Michael Hannon

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:

  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=1316195401.36711.YahooMailNeo@web161909.mail.bf1.yahoo.com \
    --to=jm_hannon@yahoo.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).