Hi:
Nicolas, I finished the first pass for simplification for the
org-e-man.el. There is probably more that can be removed, but I'm
feeling very sleepy right now...
In other news:
One thing I wanted to know if I could could replicate a document with
all the brandings that we use at work. I mana
Nicolas Goaziou writes:
> 1. Please do not leave trailing parenthesis (i.e at line 228).
Actually, it closes on line 306. I was surprised when you mentioned it
being that I use paredit mode to make sure that I do not leave trailing
parenthesis (because... I do leave them :) )
This defcustom wi
Nicolas Goaziou 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)
Hello,
It sure looks interesting.
Here are a few comment about org-e-man.el.
1. Please do not leave trailing parenthesis (i.e at line 228).
2. You can remove every `declare-function'. You only need to
(require 'org-export)
in the file header, actually.
3. You can remove `org-e-man-bab
On Tue, Jul 17, 2012 at 08:04:03PM -0400, Luis Anaya wrote:
>
> Man page
>http://ppl.ug/G1D9Y4fIwXA/
> PDF
>http://ppl.ug/1R5aCF_CmAE/
>
Aboslutely amazing! Great job Luis. :)
--
Suvayu
Open source is the future. It sets us free.
Nicolas Goaziou writes:
All right fine... I went all crazy :)
Centered text?
Yes. Implemented centered block in man pages. This is probably one of
the reasons the Org exporter enables the creation of complex
typesetting. In this case, I'm using the .ce groff command to centralize
the text. .ce
Nicolas Goaziou writes:
> 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.
Ok folks:
I created an exporter for man page based on the groff one. It probably
has mo
Nicolas Goaziou writes:
Hi:
>
> 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
Hello,
Luis Anaya writes:
> It might be easier to implement a typesetter for MAN pages in muse mode
> because it has a simpler rendering framework. It may also be a more
> appropriate platform considering that MAN pages do not have a lot of
> formatting requirements, when they are compared to
Nicolas Goaziou writes:
> You just have to put
>
> (add-to-list 'org-element-block-name-alist
>'("GROFF" . org-element-export-block-parser))
>
> in org-e-groff.el so BEGIN_GROFF/END_GROFF blocks are treated as export
> blocks again. No need to remove anything in your text pre-p
Hello,
Luis Anaya writes:
>- The change with the largest imapct on my code had to do with
> the BEGIN_GROFF/END_GROFF pairs in which now invokes the special
> block function and process the enclosed text through the plain-text
> function. Originally these were passed throug
Avdi Grimm writes:
I should have said that the idea *does have* merit and deserves some
thought. Sorry for the mix up. :(
--
Luis Anaya
papo anaya aroba hot mail punto com
"Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Avdi Grimm writes:
> Does this mean that creating manpages from org source is now a
> possibility?
Hmm...
Not right now... berause of the different macro package that man pages uses
for rendering compared to the one used in Org which is based on the MM
package.
However, one thing that got me
Does this mean that creating manpages from org source is now a possibility?
On Mon, Jul 16, 2012 at 12:38 PM, Luis Anaya wrote:
> Hi:
>
> 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
Nicolas Goaziou writes:
> Luis Anaya writes:
>> The only change I can see is the one to add the ATTR_GROFF string to get the
>> :attr_groff key in info.
>
> This is already the case since a recent patch. ATTR_SOMETHING appears
> automatically as :attr_something in element/object properties.
Ni
Nicolas Goaziou writes:
> Luis Anaya writes:
> This is already the case since a recent patch. ATTR_SOMETHING appears
> automatically as :attr_something in element/object properties.
I remember you mentioned it but it seems that I pulled the git repo too
soon. What I'll do is to refresh my deve
Luis Anaya writes:
> The only change I can see is the one to add the ATTR_GROFF string to get the
> :attr_groff key in info.
This is already the case since a recent patch. ATTR_SOMETHING appears
automatically as :attr_something in element/object properties.
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
>> let you discuss this with Nicolas, of course.
>
> AFAICT, these are just older versions of org-export.el and
> org-element.el. There are no new features added.
Most likely that we missed commits between the latest one and the one
I pulled from git. Do not update org-
Hello,
Bastien writes:
> If you need to backport some changes from your org-export/element I
> let you discuss this with Nicolas, of course.
AFAICT, these are just older versions of org-export.el and
org-element.el. There are no new features added.
> Also, from the preambule of your files, I
Hi Luis,
Luis Anaya 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 *gre
Hi:
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.
Efforts will be spent on clean-up, stability and
21 matches
Mail list logo
