emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Leonard Randall <leonard.a.randall@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: 2 issues with Include function
Date: Thu, 17 Sep 2015 09:26:13 +0200	[thread overview]
Message-ID: <87fv2dv756.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAMRQoAm49V84PKGgkaxQQ6CrSxA86ERXUSAKqHgiQ=046xQP_A@mail.gmail.com> (Leonard Randall's message of "Mon, 14 Sep 2015 19:41:51 +0100")

Hello,

Leonard Randall <leonard.a.randall@gmail.com> writes:

> I noticed 2 more issues with the include function on latex export.

I cannot reproduce any of these. Could you upgrade Org and try again?

> The first, is that when I make an id link between 2 included files,
> the exporter gives the section associated with the linked header the
> same label as the header where the link is located. So for instance if
> I include two files which include the following contents.
>
> --- Included File 1 ---
> * Headline 4
> I develop this point in [[id:beb44a5e-fc8b-4597-8dc1-0fb0a6d3a346]].
> --- ---
> --- Included File 2
> ** Headline 6.2
> :PROPERTIES:
> :ID:       beb44a5e-fc8b-4597-8dc1-0fb0a6d3a346
> :END:
> --- ---
>
> Headline 4 and Headline 6.2 will be given the same label, and so the link
> will point to headline 4, instead of Headline 6.2.

I get

  \section{Headline 4}
  \label{sec:orgheadline2}
  I develop this point in \ref{sec:orgheadline1}.
  \section{Headline 6.2}
  \label{sec:orgheadline1}

> The second problem is that if the include function is narrowed to a
> specific headline using a custom id, and there are footnotes defined at the
> very bottom of that headline, the final footnote in the section will not
> have a closing bracket.
>
> If I have the following master file and included file.
>
> --- Master file ---
> #+INCLUDE: "./1WorkingDraft.org::#Chapter1"
> --- ---
>
> --- 1WorkingDraft.org ---
> * Chapter 1 Title
> :PROPERTIES:
> :CUSTOM_ID: Chapter1
> :END:
> Here is a some text with a footnote[fn:1]. Here is some more text.
> ...
> [fn:1] Here is the definition.
>
> * Other heading or end of file
> --- ---
> I get latex export that includes something like this.
>
> ---
> \chapter{Chapter 1 Title}
> \label{sec:orgheadline11}
> Here is some text with a footnote \footnote{Here is the definition..Here is
> some more text.
> ...
> \end document

I get

  \section{Chapter 1 Title}
  \label{sec:orgheadline1}
  Here is a some text with a footnote\footnote{Here is the definition.}. Here is some more text.
  \ldots{}


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2015-09-17  7:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 18:41 2 issues with Include function Leonard Randall
2015-09-17  7:26 ` Nicolas Goaziou [this message]
2015-09-17  8:00   ` Leonard Randall

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=87fv2dv756.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=leonard.a.randall@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).