emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Luis Anaya <papoanaya@hotmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org mode export to Groff MM. Feature Freeze
Date: Mon, 16 Jul 2012 19:06:48 +0200	[thread overview]
Message-ID: <87vchnab4n.fsf@altern.org> (raw)
In-Reply-To: <BLU0-SMTP1564251A73C1E348395EFAAB7D40@phx.gbl> (Luis Anaya's message of "Mon, 16 Jul 2012 12:38:52 -0400")

Hi Luis,

Luis Anaya <papoanaya@hotmail.com> writes:

> I wanted to let you know that the development for the org-export
> exporter to groff is in feature freeze. Everything that I thought up
> that was useful has been coded. There might be other useful things to
> do, but right now... my brain is mush.  

Wow, it's *great*.  Congrats for implementing this!

The examples PDF you gave looks nice.

> Efforts will be spent on clean-up, stability and documentation. 
> Recent items added have been :
>   * Fixed issue with planner output. 
>   * Added optios for hyphenation and right justification control. 
>   * Bug fixes

Thanks again for this.  I tested org-e-groff.el and first loaded your
version of org-export.el and org-element.el but maybe I should not have
loaded first, as I get this error:

  if: Cannot read file "/tmp/reshilite11886tjl"

I have full read/write over /tmp/.

Do you have this too?

If you need to backport some changes from your org-export/element I 
let you discuss this with Nicolas, of course.

Also, from the preambule of your files, I assume you already signed 
the FSF copyright papers.  Did you?  If not, are you willing to sign 
them?  It does not prevent us for including org-e-groff.el into
contrib/lisp/ but this will be mandatory if you want this feature 
to be in core Org.



  reply	other threads:[~2012-07-16 17:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.99.1342454425.6558.emacs-orgmode@gnu.org>
2012-07-16 16:38 ` Org mode export to Groff MM. Feature Freeze Luis Anaya
2012-07-16 17:06   ` Bastien [this message]
2012-07-16 17:20     ` Nicolas Goaziou
2012-07-16 18:35       ` Luis Anaya
2012-07-16 20:36         ` Nicolas Goaziou
2012-07-16 21:22           ` Luis Anaya
2012-07-17  1:35           ` Luis Anaya
2012-07-17  7:50             ` Nicolas Goaziou
2012-07-17  8:53               ` Luis Anaya
     [not found]     ` <BLU0-SMTP243814C6971CC983CEECAFBB7D40@phx.gbl>
2012-07-16 17:42       ` FW: " Luis Anaya
2012-07-16 20:18         ` Bastien
2012-07-17  1:56   ` Avdi Grimm
2012-07-17  2:50     ` Luis Anaya
2012-07-17 10:20       ` Nicolas Goaziou
2012-07-17 14:06         ` Luis Anaya
2012-07-17 18:08         ` Luis Anaya
2012-07-18  0:04         ` Luis Anaya
2012-07-18  1:23           ` Suvayu Ali
2012-07-19 15:33           ` Nicolas Goaziou
2012-07-19 19:09             ` Luis Anaya
2012-07-20  0:07             ` Luis Anaya
2012-07-20  1:46             ` Luis Anaya
2012-07-17  2:53     ` Luis Anaya

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:

  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=87vchnab4n.fsf@altern.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=papoanaya@hotmail.com \


* 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


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).