From: Florian Beck <fb@miszellen.de>
To: Bastien <bzg@altern.org>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: `org-export-define-backend' and its friends are now defuns (was: Build fail with emacs 24.3.1)
Date: Wed, 20 Mar 2013 20:03:52 +0100 [thread overview]
Message-ID: <8738vpvqp3.fsf_-_@sophokles.streitblatt.de> (raw)
In-Reply-To: <87sj3rrzim.fsf@bzg.ath.cx> (Bastien's message of "Tue, 19 Mar 2013 18:14:17 +0100")
Bastien <bzg@altern.org> writes:
> Anyway, `org-export-define-backend' and its friends are
> now defuns, since there is no good reason for them to be macros.
This broke my setup and I had to dig (git log -p) to figure out what to
do (basically quote everything)
Instead of
(org-export-define-derived-backend my-latex latex
:translate-alist ((template . my-latex-template-fun)))
write
(org-export-define-derived-backend 'my-latex 'latex
:translate-alist '((template . my-latex-template-fun)))
[There are now double quotes in the ascii backend, which I guess are not
needed.]
Obvious, when you think about it, but I'm a bit dense when the
byte-compiler tells me that my-latex-template-fun is a malformed function.
A little more prominent warning would have been much appreciated.
--
Florian Beck
next prev parent reply other threads:[~2013-03-20 19:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 7:39 Build fail with emacs 24.3.1 Neuwirth Erich
2013-03-13 11:58 ` Bastien
2013-03-13 12:53 ` Andreas Röhler
2013-03-13 12:56 ` Bastien
2013-03-13 20:07 ` Achim Gratz
2013-03-14 2:30 ` Bastien
2013-03-14 8:26 ` Achim Gratz
2013-03-14 11:26 ` Bastien
2013-03-14 12:28 ` Bastien
2013-03-14 19:09 ` Achim Gratz
2013-03-19 17:14 ` Bastien
2013-03-20 19:03 ` Florian Beck [this message]
2013-03-20 22:58 ` `org-export-define-backend' and its friends are now defuns Bastien
2013-05-19 14:36 ` Build fail with emacs 24.3.1 Achim Gratz
2013-05-20 10:13 ` Bastien
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=8738vpvqp3.fsf_-_@sophokles.streitblatt.de \
--to=fb@miszellen.de \
--cc=Stromeko@nexgo.de \
--cc=bzg@altern.org \
--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).