emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: LaTeX export - can't skip a heading level
Date: Wed, 21 Mar 2012 08:26:30 +0100	[thread overview]
Message-ID: <87iphywh21.fsf@Rainer.invalid> (raw)
In-Reply-To: 30065.1332285895@alphaville

Nick Dokos <nicholas.dokos@hp.com> writes:
>> 
>> Especially as this is a limitation of LaTeX, not the exporter.
>> 
>> :-)
>
> Not true - the following compiles with no problems:

Yes, LaTeX doesn't really enforce it, but it makes the assumption of
"correct nesting".  It's been a few years since I tried something like
you've posted, but I've quickly learned that funny things happen when
your document grows to a more realistic size (it had to do with how the
counters are interacting).  So I've stopped doing it and have never
looked back.  If you must, you can provide your own sectioning commands
in LaTeX that handle this situation more gracefully, but that's really a
bit much to ask of an org exporter, don't you think?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2012-03-21  7:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 19:27 LaTeX export - can't skip a heading level Richard Stanton
2012-03-20 19:31 ` TODO items as part of an itemized list? Richard Stanton
2012-03-20 23:44   ` Bastien
2012-03-21 20:40     ` Richard Stanton
2012-03-21 21:18       ` Nick Dokos
2012-03-26 17:41         ` Bastien
2012-03-21 21:43   ` Samuel Wales
2012-03-20 19:55 ` LaTeX export - can't skip a heading level Nick Dokos
2012-03-20 19:57   ` Richard Stanton
2012-03-20 20:30   ` Nick Dokos
2012-03-20 22:05     ` Achim Gratz
2012-03-20 23:24       ` Nick Dokos
2012-03-21  7:26         ` Achim Gratz [this message]
2012-03-21 12:12           ` Nick Dokos

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=87iphywh21.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    /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).