[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] template for writing Emacs manuals in Org

From: Jonathan Leech-Pepin
Subject: Re: [O] template for writing Emacs manuals in Org
Date: Wed, 18 May 2016 10:56:02 -0400
User-agent: K-9 Mail for Android


On May 18, 2016 5:21:06 AM EDT, Rasmus <address@hidden> wrote:
>Nick Dokos <address@hidden> writes:
>> I believe the main obstacle is that the emacs policy requires a
>> manual for all its component parts.
>What is the "component parts"?  I couldn't find the definition.
>>  If that can be generated automatically from the org document, then
>> objections probably disappear. Of course, Bastien might object to the
>> extra effort required to do the conversion, but if the conversion is
>> indeed completely automatic (or, perhaps more likely, a volunteer can
>> found to take care of the conversion and any problems that might
>> then he might be amenable to it. But it would be an extra step
>> at release time and would require some coordination.
>My issue is all the damn macros.  While it displays the flexibility of
>Org, it also makes Org-for-texinfo-manuals less appealing.  I don’t
>to learn new mini documentation language for each manual I might send
>patches to.
>Maybe a "Library-of-Macros" would go some of the way of at least making
>feel less ad-hoc?
>Another annoyance.  When I see something like the an index right after
>headline, I really would like to put the index into the properties
>     ** Installation
>        :PROPERTIES:
>        :DESCRIPTION: How to install a downloaded version of Org-mode
>        :END:
>     {{{cindex(installation)}}}

I’m trying to remember why I didn’t implement indexes as properties (it may 
well have been because I simply didn’t consider it).  Assuming there’s nothing 
in the exporter to prevent converting properties to text after headlines it 
could work. Treat comma separated values as separate entries.

Then using the macro would only be needed if indexing at content rather than at 
a headline (use lower level headlines that do not become nodes and it could 
still work).

>Aside: I’ve been wanting a drawer property for inserting text just
>headings (and maybe just after headings) for a while, e.g.
>It would also be useful for latex, e.g.
>    * Proofs
>      :EXPORT_LATEX_BEFORE: \appendix
>      :INSERT_BEFORE: @@latex:\appendix@@
>      :END:


reply via email to

[Prev in Thread] Current Thread [Next in Thread]