From: Carsten Dominik <carsten.dominik@gmail.com>
To: David Maus <dmaus@ictsoc.de>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus.pank@gmail.com>
Subject: Re: LaTeX exporter #+INCLUDE bug
Date: Thu, 13 Jan 2011 13:14:45 +0100 [thread overview]
Message-ID: <FF96B36D-05CE-431F-8D58-CFB285D9F76C@gmail.com> (raw)
In-Reply-To: <87sjx2kweh.wl%dmaus@ictsoc.de>
On Jan 9, 2011, at 3:02 PM, David Maus wrote:
> At Mon, 20 Dec 2010 19:12:33 +0000 (UTC),
> Rasmus wrote:
>>
>> Hi,
>> I think there might be a bug when using #+INCLUDE and the LaTeX
>> exporter. The
>> content of the included file is exported twice, although slightly
>> different in
>> each case. I experience this when I include org-files starting with
>> a headline,
>> i.e. "*".
>>
>> I use Org-mode 7.4 with GNU Emacs 24.0.50.1 (x86_64-unknown-linux-
>> gnu, GTK+
>> Version 2.22.1)
>
> I can confirm this with
>
> Org-mode version 7.4 (release_7.4.135.g84087)
>
> GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
> of 2010-12-11 on raven, modified by Debian
Yes. This is a bug and a bit hard to fix.
I only happens if the #+include line is before the
first headline in the buffer.
I am afraid I do not have a simple solution.
- Carsten
>
> Best,
> -- David
> --
> OpenPGP... 0x99ADB83B5A4478E6
> Jabber.... dmjena@jabber.org
> Email..... dmaus@ictsoc.de
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-01-13 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 19:12 LaTeX exporter #+INCLUDE bug Rasmus
2011-01-09 14:02 ` David Maus
2011-01-13 12:14 ` Carsten Dominik [this message]
2011-01-15 13:52 ` Rasmus Pank Roulund
2011-02-12 15:02 ` Bastien
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=FF96B36D-05CE-431F-8D58-CFB285D9F76C@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus.pank@gmail.com \
/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).