From: tsd@tsdye.com (Thomas S. Dye)
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Unexpected macro error
Date: Wed, 19 Nov 2014 07:20:15 -1000 [thread overview]
Message-ID: <m2sihfxg34.fsf@tsdye.com> (raw)
Aloha all,
A document I've been working on for several weeks broke recently without
changes on my part. However, I've been tracking the master git branch
every once in a while and I suspect some change in Org is the culprit.
Org-mode version 8.3beta (release_8.3beta-580-g787733 @ /Users/dk/.emacs.d/src/org-mode/lisp/)
I haven't tried to make an ECM because I don't know what the problem
could be. Here is a backtrace:
Debugger entered--Lisp error: (error "Undefined Org macro: ad; aborting.")
signal(error ("Undefined Org macro: ad; aborting."))
error("Undefined Org macro: %s; aborting." "ad")
org-macro-replace-all((("author" . #("Thomas S. Dye" 0 13 (:parent (#("Thomas S. Dye" 0 13 (:parent #4)))))) ("date" . "\\today") ("email" . "tsd@tsdye.com") ("title" . #("Dating human dispersal in Remote Oceania: A view from Hawai`i" 0 61 (:parent (#("Dating human dispersal in Remote Oceania: A view from Hawai`i" 0 61 (:parent #4))))))) finalize)
org-export-as(latex nil nil nil (:output-file "./dispersals.tex"))
org-export-to-file(latex "./dispersals.tex" nil nil nil nil nil #[(file) "\301\b!\207" [file org-latex-compile] 2])
org-latex-export-to-pdf(nil nil nil nil)
(org-open-file (org-latex-export-to-pdf nil s v b))
(if a (org-latex-export-to-pdf t s v b) (org-open-file (org-latex-export-to-pdf nil s v b)))
(lambda (a s v b) (if a (org-latex-export-to-pdf t s v b) (org-open-file (org-latex-export-to-pdf nil s v b))))(nil nil nil nil)
org-export-dispatch(nil)
call-interactively(org-export-dispatch nil nil)
command-execute(org-export-dispatch)
The error message refers to a macro, ad. I don't have an "ad" macro.
Where does this come from?
The next header line, after the headers that become macros, is
#+ADDRESS:, which starts with "ad", although the case is different.
Also, the string "ad" occurs frequently in my writing as the path in a
custom link that sets the path as small caps in LaTeX output,
e.g. [[sc:ad][AD]].
You can see that I'm groping in the dark. Any suggestions how I might
go about debugging this?
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
next reply other threads:[~2014-11-19 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 17:20 Thomas S. Dye [this message]
2014-11-21 22:55 ` Unexpected macro error Nicolas Goaziou
2014-11-22 5:13 ` 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=m2sihfxg34.fsf@tsdye.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).