emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Luis Anaya <papoanaya@hotmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org mode export to Groff MM. Feature Freeze
Date: Thu, 19 Jul 2012 15:09:20 -0400	[thread overview]
Message-ID: <BLU0-SMTP309296061C027408EDED660B7D90@phx.gbl> (raw)
In-Reply-To: <878vefbwa7.fsf@gmail.com> (Nicolas Goaziou's message of "Thu, 19 Jul 2012 17:33:36 +0200")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
> It sure looks interesting.

Well, I did it in the spur of the moment. What I'll do is to open a
ticket for each of the item to keep track of them. 

> Here are a few comment about org-e-man.el.
> 1. Please do not leave trailing parenthesis (i.e at line 228).

Well, I guess that paredit does not work as good as I though. I have to
check those over, thanks. 

> 2. You can remove every `declare-function'. You only need to
>     (require 'org-export)
>    in the file header, actually.
> 5. Do you really need something as complicated as `org-e-man-classes'?

The only thing I can think of is to use to determine what man page
you're creating. But that can be done through the use of a list, or just
place the man number as a variable. 

I have to leave it for the MM one though, it'll be evident when I'm with my
branding exercise and show the results. 

> 14. In general, try to remove as much unused stuff as possible.

Yes, it's on the queue of things to do. Work is heating up, though. But
what'll do is keep track those in github so I can address those 
as I continue with development. (and in org as well :) )


Luis R. Anaya
papo anaya aroba hot mail punto com
"Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo

  reply	other threads:[~2012-07-19 19:09 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
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 [this message]
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=BLU0-SMTP309296061C027408EDED660B7D90@phx.gbl \
    --to=papoanaya@hotmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.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).