emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Unnumbered sections in LaTeX export
Date: Mon, 14 Sep 2009 21:43:17 -1000	[thread overview]
Message-ID: <70DA6B2C-D450-4679-AF11-C35EBCA21743@tsdye.com> (raw)
In-Reply-To: <87ocpcvq2t.fsf@gmx.de>


On Sep 14, 2009, at 5:34 PM, Sebastian Rose wrote:

> "Thomas S. Dye" <tsd@tsdye.com> writes:
>> On Sep 14, 2009, at 10:21 AM, Sebastian Rose wrote:
>>
>>> "Thomas S. Dye" <tsd@tsdye.com> writes:
>>>> Aloha all,
>>>>
>>>> The variable org-export-latex-classes has a specification for  
>>>> unnumbered
>>>> sections but I haven't found any documentation how to mark  up  
>>>> the org file
>>>> to
>>>> activate them.  I might have missed something  obvious.  Could  
>>>> someone give
>>>> me a
>>>> pointer to documentation or some  help how to markup the org file?
>>>>
>>>> All the best,
>>>> Tom
>>>
>>> Thomas,
>>>
>>> Are you looking for
>>>
>>>  M-x customize-variable RET org-export-with-section-numbers RET
>>>
>>> ??
>>>
>>> As Matt wrote, per file setting is:
>>>
>>> #+OPTIONS: num:nil
>>>
>>>
>>>
>>>
>>> Sebastian
>>
>> Yes, that is it.  Thanks!
>>
>> Is there any way to set this for an individual headline?  Or, is it  
>> effective
>> only for the entire file, or portion of file, that is  exported?
>>
>> All the best,
>> Tom
>
>
> No. There is just the global default (`org-export-with-section- 
> numbers')
> and the per-file setting. Both entire files.
>
>
> Best wishes
>
>
>   Sebastian

Thanks Sebastian.  I appreciate the expert assistance.  I have a  
simple export to Beamer working and was trying to implement automatic  
export of columns, too.  The starred sections were going to be  
placeholders for the columns heading level when it wasn't used.  I've  
found that skipping a headline level in the source causes the latex  
exporter to skip over subsequent inferior levels, so it isn't possible  
to assign a heading level to columns and then use them or not as the  
case requires.  I'm actually quite happy with the simple export I have  
working.  Beamer templates that show the document structure are easy  
to write to using org-mode, where document structure is so important.

All the best,
Tom

  parent reply	other threads:[~2009-09-15  7:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-13 21:06 Unnumbered sections in LaTeX export Thomas S. Dye
2009-09-14  1:26 ` Matt Lundin
2009-09-14 20:21 ` Sebastian Rose
     [not found]   ` <1CCB79D7-DB7A-4274-B6E8-F53EE2B69638@tsdye.com>
     [not found]     ` <87ocpcvq2t.fsf@gmx.de>
2009-09-15  7:43       ` Thomas S. Dye [this message]
     [not found]         ` <87iqfkayuc.fsf@gmx.de>
2009-09-15 22:04           ` Thomas S. Dye
2009-09-18 17:29             ` Carsten Dominik
2009-09-19 16:32               ` Thomas S. Dye

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=70DA6B2C-D450-4679-AF11-C35EBCA21743@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastian_rose@gmx.de \
    /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).