From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Re: unnumbered subsections in latex export Date: Wed, 23 Mar 2011 11:02:40 -0400 Message-ID: <7864.1300892560@alphaville.dokosmarshall.org> References: <20110322051038.21655c80@kuru.homelinux.net> <80d3lj9wj6.fsf@somewhere.org> <20110322053134.669127e9@kuru.homelinux.net> <8999.1300804510@alphaville.dokosmarshall.org> <20110322160814.227fc53f@bhishma.homelinux.net> <27844.1300836065@alphaville.usa.hp.com> <87ipv9gbst.fsf@gnu.org> Reply-To: nicholas.dokos@hp.com Return-path: Received: from [140.186.70.92] (port=43564 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q2PaN-0004bi-J2 for emacs-orgmode@gnu.org; Wed, 23 Mar 2011 11:03:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q2PaM-0007xv-Cj for emacs-orgmode@gnu.org; Wed, 23 Mar 2011 11:02:59 -0400 Received: from vms173009pub.verizon.net ([206.46.173.9]:44405) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q2PaM-0007xe-9R for emacs-orgmode@gnu.org; Wed, 23 Mar 2011 11:02:58 -0400 Received: from alphaville.dokosmarshall.org ([unknown] [173.76.32.106]) by vms173009.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LII00K1XN4GY120@vms173009.mailsrvcs.net> for emacs-orgmode@gnu.org; Wed, 23 Mar 2011 10:02:47 -0500 (CDT) In-reply-to: Message from Bastien of "Wed, 23 Mar 2011 15:18:42 BST." <87ipv9gbst.fsf@gnu.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org, nicholas.dokos@hp.com Bastien wrote: > Hi Nick, > > Nick Dokos writes: > > > Suvayu Ali wrote: > > > >> This works too, but Lawrence's patch makes it much easier and > >> probably works for other export formats too. Thanks a lot. :) > > > > No doubt Lawrence's patch can be extended to work for other exports, but > > it's not there yet: each exporter would need a change similar to the one > > that he made to the LaTeX exporter. > > Let's handle this change exporter by exporter. The longest trip starts > with the first step :) > Sorry, I sent my previous comment without reading ahead for this. I still would like to see some discussion on this, though. Thanks, Nick