Re: [O] org-e-groff-export-to-groff produces empty output file

[Luis Anaya]

Hi:

When I commited that returned the conflict warning, I noticed that they were removed.

I cannot think of a use for those while typesetting in Groff, other than send Groff commands with a LaTeX instruction (awkward...). If this is the case, those two routines should be removed from the exporter as well.

Luis


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

Hello,

Luis Anaya

writes:

> I can remove and push it (if allowed). I know that there was a change
> in the server being that git complained about the SSL certificate.

I've regained push access. So it should be fixed now. I let you
double-check the commits.

As a side note, there was a typo in some element types (latex-fragment
and latex-environment) so they were ignored by the Groff back-end. I've
fixed their name, but, since I don't know what you want to do with them,
I've commented them out from back-end definition. Thus, they are still
ignored (see lines 68-69 in the file). I let you decide what to do with
them.


Regards,

--
Nicolas Goaziou