From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Elston Subject: latex enumeration issue Date: Tue, 02 Feb 2010 14:08:42 -0800 Message-ID: <4B68A26A.3030509@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NcQve-0004as-8F for emacs-orgmode@gnu.org; Tue, 02 Feb 2010 17:09:02 -0500 Received: from [199.232.76.173] (port=40987 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NcQvd-0004aj-Sr for emacs-orgmode@gnu.org; Tue, 02 Feb 2010 17:09:01 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NcQvZ-0007ew-0q for emacs-orgmode@gnu.org; Tue, 02 Feb 2010 17:09:01 -0500 Received: from qmta11.emeryville.ca.mail.comcast.net ([76.96.27.211]:42243) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NcQvY-0007ei-G8 for emacs-orgmode@gnu.org; Tue, 02 Feb 2010 17:08:56 -0500 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: org-mode emacs-orgmode A year ago Flavio de Souza asked a question about latex enumerations that is similar to a problem I now have. The answer given then was a workaround that doesn't apply in my case. This stems from my project of using a single file to maintain source for generating my class notes *and* student handouts for my classes. This allows me to take advantage of the common outline and common text while specifying text that should go into only one or the other document. I manage to do this by something like: * Common heading Some common text ** A common subheading More common text *** :handouts: Something for handouts only *** :both: More common text *** :notes: My class notes text *** :both: More common text I have a makefile which creates a temporary .org file by prepending a specific header on this file for each type of output (handouts or notes), exporting to a latex file, running a perl script to remove any (sub)+sections with just the tags in them, and running pdflatex to generate the output. So far, so good. However, I ran into a problem with enumerations. Sometimes I have enumerations in my original org file which are separated by the 'empty' sectioning commands. This ends the enumeration and the next enumerated item starts a new one. The result is a set of enumerations with a single element in it. I get something like: 1. Blah handout-specific text 1. More Blah etc. These should really have been 1, 2, etc. The only workaround I have so far is to make all these items lists instead of enumerations. This works OK but they would make much more sense as enumerations. Is there anything I can do here? Mark