From: Bastien <bastienguerry@googlemail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: LaTeX export bug (skipping outline levels)
Date: Sat, 03 Oct 2009 05:42:20 +0800 [thread overview]
Message-ID: <87ws3djww3.fsf@bzg.ath.cx> (raw)
In-Reply-To: <D3D888A6-CAC2-44A5-9F14-20FA9C0231FF@gmail.com> (Carsten Dominik's message of "Fri, 2 Oct 2009 08:44:07 +0200")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> yes, the LaTeX exporter is picky about correct outline structure.
> I am not sure if this can be changed without breaking something.
> Bastien, can you see this?
Now I can see (my @gnu.org email was down for two days.)
But I don't see any straightforward way to fix it, sorry.
--
Bastien
prev parent reply other threads:[~2009-10-02 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 14:04 LaTeX export bug (skipping outline levels) Eric Schulte
2009-10-02 6:44 ` Carsten Dominik
2009-10-02 21:42 ` Bastien [this message]
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=87ws3djww3.fsf@bzg.ath.cx \
--to=bastienguerry@googlemail.com \
--cc=carsten.dominik@gmail.com \
--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).