[O] Re: [Accepted] org-export-preprocess-string: Use backend var

[Matt Lundin]

Jambunathan K <address@hidden> 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