From: Matt Lundin <mdl@imapmail.org>
To: emacs-orgmode@gnu.org
Subject: Re: [Accepted] org-export-preprocess-string: Use backend var
Date: Sat, 19 Mar 2011 09:29:27 -0400 [thread overview]
Message-ID: <87lj0bfdc8.fsf@fastmail.fm> (raw)
In-Reply-To: <81vd0472e9.fsf@gmail.com> (Jambunathan K.'s message of "Mon, 28 Feb 2011 18:16:22 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
> Bastien
>
>>> + ;; Backend-specific preprocessing
>>> + (let* ((backend-name (symbol-name backend))
>>> + (f (intern (format "org-export-%s-preprocess" backend-name))))
>>> + (require (intern (concat "org-" backend-name)) nil)
>>> + (funcall f parameters))
>
> A few words of explanation from my side.
>
> Summary: Facilitate transparent plugging-in of per-backend
> pre-processing logic to the org exporter.
>
> Jambunathan K.
>
This patch (0135cb9c) breaks Wes Hardaker's generic export (in contrib).
Since the backend is nil, the following line causes org-export to try to
require org-nil:
(require (intern (concat "org-" backend-name)) nil)
--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (file-error "Cannot open load file" "org-nil")
require(org-nil nil)
--8<---------------cut here---------------end--------------->8---
I ask because even though org-export-generic.el is a contributed
package, an option to call it is hard-coded into org-export:
--8<---------------cut here---------------start------------->8---
\[g] export using Wes Hardaker's generic exporter
--8<---------------cut here---------------end--------------->8---
Best,
Matt
next prev parent reply other threads:[~2011-03-19 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 17:00 [PATCH] org-export-preprocess-string: Use backend var Jambunathan K
2011-02-28 11:20 ` [Accepted] " Bastien Guerry
2011-02-28 12:46 ` Jambunathan K
2011-02-28 13:56 ` Bastien
2011-03-19 13:29 ` Matt Lundin [this message]
2011-03-19 20:33 ` Matt Lundin
2011-02-28 11:22 ` [PATCH] " 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=87lj0bfdc8.fsf@fastmail.fm \
--to=mdl@imapmail.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).