From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Leech-Pepin Subject: Re: template for writing Emacs manuals in Org Date: Wed, 18 May 2016 10:56:02 -0400 Message-ID: <4BDEAAA9-55A2-4886-80E1-ECF273D4C7E1@gmail.com> References: <87eg955clk.fsf@ericabrahamsen.net> <87wpmt7u5i.fsf@gmx.us> <87r3d1u5yn.fsf@saiph.selenimh> <87eg91ten0.fsf@saiph.selenimh> <87a8jou24u.fsf@saiph.selenimh> <87futgikda.fsf@alphaville.usersys.redhat.com> <87oa83afi5.fsf@gmx.us> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45825) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b32tO-0001qz-AY for emacs-orgmode@gnu.org; Wed, 18 May 2016 10:56:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b32tM-0001Gf-2E for emacs-orgmode@gnu.org; Wed, 18 May 2016 10:56:09 -0400 Received: from mail-vk0-x243.google.com ([2607:f8b0:400c:c05::243]:35334) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b32tL-0001GS-U1 for emacs-orgmode@gnu.org; Wed, 18 May 2016 10:56:07 -0400 Received: by mail-vk0-x243.google.com with SMTP id e126so7482831vkb.2 for ; Wed, 18 May 2016 07:56:07 -0700 (PDT) In-Reply-To: <87oa83afi5.fsf@gmx.us> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Rasmus , emacs-orgmode@gnu.org Hi, On May 18, 2016 5:21:06 AM EDT, Rasmus wrote: >Hi, > >Nick Dokos writes: > >> I believe the main obstacle is that the emacs policy requires a >texinfo >> 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 >any >> 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 >be >> found to take care of the conversion and any problems that might >arise), >> then he might be amenable to it. But it would be an extra step >required >> 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 >want >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 >it >feel less ad-hoc? > >Another annoyance. When I see something like the an index right after >a >headline, I really would like to put the index into the properties >drawer: > > ** 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 >before >headings (and maybe just after headings) for a while, e.g. > > EXPORT_BACKEND_{BEFORE, AFTER}, or > INSERT_{BEFORE, AFTER} > >It would also be useful for latex, e.g. > > * Proofs > :PROPERTIES: > :EXPORT_LATEX_BEFORE: \appendix > :INSERT_BEFORE: @@latex:\appendix@@ > :END: > >Rasmus -- Jon