emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Export problem with source code blocks
Date: Sat, 30 Mar 2013 09:29:19 -1000	[thread overview]
Message-ID: <m1ehew1yb4.fsf@poto.myhome.westell.com> (raw)

Aloha all,

The following code block executes fine in the Org buffer, and it
exported cleanly on January 18th, but fails on export to LaTeX with a
recent version of Org from the git repo. Here is the error message:

  executing Emacs-Lisp code block (plos-one-start)...

  Debugger entered--Lisp error: (void-function first)
    (first row)

#+name: plos-one-start
#+header: :var tab=author-table
#+header: :var title="A Regional Chronology"
#+header: :results raw :wrap latex
#+header: :exports results
#+begin_src emacs-lisp
  (defun author-name (recs)
    "Format the author name list."
    (let ((i 0))
      (mapcar (lambda (row)
                (concat (format "%s$^{%d%s" (first row)
                                (incf i)
                                (if (equal "yes" (eighth row)) ",\\ast" ""))
                        (if (equal row (car (last recs))) "}$" "}$,")))
              recs)))
  
  (defun author-affiliation (recs)
    "Format the author affiliation list."
    (let ((i 0))
      (mapcar (lambda (row)
                (format "\\bf{%d} %s, %s, %s, %s, %s" (incf i)
                        (second row) (third row) (fourth row)
                        (fifth row) (sixth row)))
              recs)))
  (defun corresponding-email (recs)
    "Return the corresponding email."
    (mapcar (lambda (row)
              (format "%s" (if (equal "yes" (eighth row)) (seventh row) "")))
            recs))
  
  (let* ((tab (cdr (cdr tab)))
        (a (author-name tab))
        (b (author-affiliation tab))
        (c (corresponding-email tab)))
    (concat (format "\\begin{flushleft}\n{\\Large\n\\textbf{%s}\n}\n\\\\\n" title)
            (mapconcat 'identity a "\n") "\n\\\\\n"
            (mapconcat 'identity b "\n\\\\\n")
            "\n\\\\\n$\\ast$ E-mail: "
            (mapconcat 'identity c "\n")
            "\n\\end{flushleft}"))
#+end_src

#+name: author-table
| Author name   | Department                 | Institution           | City     | State | Country | Email         | Corresponding |
|---------------+----------------------------+-----------------------+----------+-------+---------+---------------+---------------|
| Thomas S. Dye | Department of Anthropology | University of Hawai`i | Honolulu | HI    | USA     | tsd@tsdye.com | yes           |

All the best,
Tom

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

             reply	other threads:[~2013-03-30 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-30 19:29 Thomas S. Dye [this message]
2013-03-30 21:29 ` Export problem with source code blocks Eric Schulte
2013-03-30 22:32   ` Thomas S. Dye

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=m1ehew1yb4.fsf@poto.myhome.westell.com \
    --to=tsd@tsdye.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).