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: Tue, 17 Jul 2012 10:06:50 -0400	[thread overview]
Message-ID: <BLU0-SMTP139B87309098F1E5E2BFFD4B7DB0@phx.gbl> (raw)
In-Reply-To: <87a9yy664p.fsf@gmail.com> (Nicolas Goaziou's message of "Tue\, 17 Jul 2012 12\:20\:38 +0200")

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


> An advantage of the new export engine is that a back-end can be as
> simple as you want it to be.  

This is correct; you bring a good point. 

> One can imagine specialized back-ends only rendering a limited set of
> Org features. As long as the set is explicitly documented in the
> back-end, there's nothing wrong with that.


But, there's more to the story. I started dabbling with muse
this morning at 4:00 AM (because that's the best time to play with
emacs, just after the ghosts go to bed :) ). I got a fairly modest
version running in muse that created a fairly believable man page.  

I realized some things during the experiment: 

1. Although the subset of MAN macros is small for the creation of man 
pages, there are things that can be done procedurally during export that
can enhance the look of the man page. The new Org backend makes this
task a lot easier because of its flexibility and the availability of all
data items through the "info" variable.   The POD to man page does that,
no reason why it cannot be done in Org. 

2. The ability to render source code, or the execution of embedded code,
would have a positive impact on the end result. 

I can work on a prototype on Org and see how it goes. 

Luis 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-17 14:07 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 [this message]
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=BLU0-SMTP139B87309098F1E5E2BFFD4B7DB0@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).