From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Luis Anaya <papoanaya@hotmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>,
Eric Schulte <eric.schulte@gmx.com>
Subject: Re: org-e-groff-export-to-groff produces empty output file
Date: Sat, 22 Sep 2012 11:32:59 +0200 [thread overview]
Message-ID: <87fw6acshg.fsf@gmail.com> (raw)
In-Reply-To: <BLU0-SMTP48E4EA39871EF02719BAD2B7980@phx.gbl> (Luis Anaya's message of "Sat, 22 Sep 2012 05:28:06 -0400")
Hello,
Luis Anaya <papoanaya@hotmail.com> 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
next prev parent reply other threads:[~2012-09-22 9:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 9:28 org-e-groff-export-to-groff produces empty output file Luis Anaya
2012-09-22 9:32 ` Nicolas Goaziou [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-22 9:58 Luis Anaya
2012-09-22 12:06 ` Nicolas Goaziou
2012-09-22 20:10 ` Luis Anaya
2012-09-24 2:18 ` Luis Anaya
2012-09-22 9:53 Luis Anaya
2012-09-22 20:11 ` Luis Anaya
2012-09-22 9:01 Luis Anaya
2012-09-22 9:03 ` Nicolas Goaziou
2012-09-20 19:38 Eric Schulte
2012-09-21 14:34 ` Ian Barton
2012-09-21 14:44 ` Robert Klein
2012-09-22 4:59 ` Robert Klein
2012-09-21 15:54 ` cberry
2012-09-21 16:11 ` Bastien
2012-09-21 17:21 ` Eric Schulte
2012-09-21 21:55 ` Luis Anaya
2012-09-21 22:50 ` Luis Anaya
2012-09-22 7:55 ` Nicolas Goaziou
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=87fw6acshg.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.com \
--cc=papoanaya@hotmail.com \
/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).