Yes, that happens. :)

If it's taken care of and push to git, I can go ahead and run regression to make sure that everything is working ok.

Luis

-------- Original Message --------
From: Nicolas Goaziou
Sent: Sat, Sep 22, 2012 03:55 AM
To: Luis Anaya
CC: Eric Schulte ; Org Mode Mailing List
Subject: Re: org-e-groff-export-to-groff produces empty output file

Hello,

Luis Anaya writes:

> Luis Anaya writes:
>
>> Eric Schulte writes:
>>
>>> Hi,
>>>
>>> Maybe I'm missing something obvious here, but I can't get org-e-groff to
>>> generate anything but an empty output file. I've boiled this down to
>
> Hi:
>
> No, you're not missing something, there's is a problem. I just ran
> regression and all the groff files are empty. My gut feeling is the
> change from the defvar to the invocation of
> `org-export-define-backend' is not mapping the different calls to
> its respective function. First thing I noticed is that the second
> parameter, is a symbol while the function expects it to be a string
> (it's passing it into a format), that may be one of the problems. I
> changed it to a string with the same results. (i. e. empty files).
>
>
> I ran it with an older version of org-e-groff.el that does not use
> this function and it runs fine with the lastest from git.
>
> Hmmm...

This is because I made a typo when defining the back-end: there
shouldn't be any quote before the first alist.

Regards,

--
Nicolas Goaziou