From: Tomas Grigera <tgrigera@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: BUG: Latex exporter bug
Date: Sat, 28 Jan 2012 14:18:13 -0300 [thread overview]
Message-ID: <CAJMNdQJafBAdE5HfwtHa1PT_Va91mScuH1uk4FT=W4-7YRCqCQ@mail.gmail.com> (raw)
In-Reply-To: <87pqe3yfw0.fsf@gnu.org>
Hi Bastien
>> I have found the following issue when exporting to Latex: a headline
>> is sometimes moved to another position when skipping a level in the
>> hierarchy. The following demonstrates the problem:
>
> This is a known issue and can't be handled with the current
> exporter. The "workaround" is to stick to a logical structure.
Sorry, I had missed when this was discussed. Thanks for your answer.
Cheers,
Tomas
prev parent reply other threads:[~2012-01-28 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 15:07 BUG: Latex exporter bug Tomas Grigera
2012-01-28 16:02 ` Bastien
2012-01-28 17:18 ` Tomas Grigera [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='CAJMNdQJafBAdE5HfwtHa1PT_Va91mScuH1uk4FT=W4-7YRCqCQ@mail.gmail.com' \
--to=tgrigera@gmail.com \
--cc=bzg@altern.org \
--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).