From: "Thomas S. Dye" <tsd@tsdye.com>
To: chris.m.malone@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: org-export-latex-classes issue
Date: Wed, 20 Oct 2010 09:49:54 -1000 [thread overview]
Message-ID: <3B241AC3-212F-4CD2-A62B-5F2339E0E313@tsdye.com> (raw)
In-Reply-To: <00163628393eae15aa0493112b25@google.com>
On Oct 20, 2010, at 9:11 AM, chris.m.malone@gmail.com wrote:
> Hi,
>
> I'm a n00b to Lisp and org-mode so please forgive me if the answer
> is obvious. I'm using version 7.01h of org-mode.
>
> I'm trying to set up a custom Latex class to use for preparing a
> document. Some Google searching showed that I need to add this class
> to the org-export-latex-classes symbol. I tried to do this in
> my .emacs file, for example following what is listed at http://orgmode.org/worg/org-tutorials/org-latex-export.php
> by adding the following to my .emacs file:
>
> (add-to-list 'org-export-latex-classes
> '("article"
> "\\documentclass{article}"
> ("\\section{%s}" . "\\section*{%s}")))
>
>
> I know that org-export-latex-default-class is already set to
> "article" but this example already shows that something is wrong.
> When I load emacs the debugger complains that org-export-latex-
> classes is an empty list:
>
> Debugger entered--Lisp error: (void-variable org-export-latex-classes)
> add-to-list(org-export-latex-classes ("article" "\
> \documentclass{article}" ("$
> eval-buffer(#<buffer *load*> nil "/home/cmalone/.emacs" nil t) ;
> Reading at$
> load-with-code-conversion("/home/cmalone/.emacs" "/home/
> cmalone/.emacs" t t)
> load("~/.emacs" t t)
> #[nil "^H\205\276^@ \306=\203^Q^@\307^H\310Q\202A^@ \311=\2033^@
> \312\307\31$
> command-line()
> normal-top-level()
>
> As far as I can tell, org-export-latex-classes is set to nil in org-
> latex.el, but this isn't loaded until the export dispatcher calls
> org-export-as-latex. Is this correct? Coincidentally, if I export to
> latex, the appropriate .tex file is created without issue.
>
> My original goal was to setup a custom Latex class - I have tried in
> the same manner as that used above for the "article" class and the
> debugger produces the same result. However, when I attempt to export
> to latex I get the error that my custom class isn't in the org-
> export-latex-classes list, presumably because of the failure in
> loading the .emacs file.
>
> Any advice?
>
> Chris_______________________________________________
Hi Chris,
My tutorial might have been over-optimistic about the ease of
configuration. Perhaps you also need this in your .emacs before you
add-to-list:
(require 'org-latex)
All the best,
Tom
next prev parent reply other threads:[~2010-10-20 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 19:11 org-export-latex-classes issue chris.m.malone
2010-10-20 19:49 ` Thomas S. Dye [this message]
2010-10-20 19:54 ` Chris Malone
2010-10-20 20:01 ` 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=3B241AC3-212F-4CD2-A62B-5F2339E0E313@tsdye.com \
--to=tsd@tsdye.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).