emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Mark Elston <m_elston@comcast.net>
Cc: org-mode emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: latex enumeration issue
Date: Wed, 3 Feb 2010 11:34:26 +0100	[thread overview]
Message-ID: <B7219DDA-641C-4750-86C2-1A1EE7076643@gmail.com> (raw)
In-Reply-To: <4B68A26A.3030509@comcast.net>

Hi Mark,

On Feb 2, 2010, at 11:08 PM, Mark Elston wrote:

> 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.


I don't understand.  Why is the text "handout-specific text" still  
there?
Do you need it between the items?  Do you want to make it part of the  
item (indentation would solve this).


>
> 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.


How does this help?

- Carsten

  reply	other threads:[~2010-02-03 10:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 22:08 latex enumeration issue Mark Elston
2010-02-03 10:34 ` Carsten Dominik [this message]
2010-02-03 20:41   ` Mark Elston
2010-02-04  2:24     ` Mark Elston
2010-02-04  3:12       ` Mark Elston
2010-02-04  4:28         ` Dan Davison
2010-02-04  7:00         ` Mark Elston
2010-02-04 10:05       ` Eric S Fraga
2010-02-06  8:18         ` Daniel Martins
2010-02-06 19:06           ` Mark Elston

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B7219DDA-641C-4750-86C2-1A1EE7076643@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=m_elston@comcast.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).