Re: [O] new exporter

[Nicolas Goaziou]

Hello,

Achim Gratz <address@hidden> writes:

> This code snippet has at last after revealed where the problem is: the
> function call to (current-buffer) gets unquoted, when it clearly needs
> to be in the expansion.  The literal expansion of the buffer content
> into the compiled bytecode is similarly explained by an unquoting of
> (buffer-string).  Here's a patch that seems to fix the compilation
> (without changelog and everything because I think you may want to check
> the rest of the new exporters for similar constructs).

Nice catch.

I think you can go ahead and commit it: your description of the problem
will be more accurate than mine.

Thank you for this investigation and, obviously, for the fix.


Regards,

-- 
Nicolas Goaziou