From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: template for writing Emacs manuals in Org Date: Wed, 18 May 2016 11:21:06 +0200 Message-ID: <87oa83afi5.fsf@gmx.us> 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> 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]:52962) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2xfK-0006ZQ-US for emacs-orgmode@gnu.org; Wed, 18 May 2016 05:21:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b2xfH-0006GB-Kt for emacs-orgmode@gnu.org; Wed, 18 May 2016 05:21:18 -0400 Received: from plane.gmane.org ([80.91.229.3]:57994) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2xfH-0006Fo-Ef for emacs-orgmode@gnu.org; Wed, 18 May 2016 05:21:15 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1b2xfG-00086l-5s for emacs-orgmode@gnu.org; Wed, 18 May 2016 11:21:14 +0200 Received: from 46.166.190.211 ([46.166.190.211]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 18 May 2016 11:21:14 +0200 Received: from rasmus by 46.166.190.211 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 18 May 2016 11:21:14 +0200 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: emacs-orgmode@gnu.org 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)}}} 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 -- ツ