emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Multi-file and master files
Date: Wed, 01 Oct 2014 12:57:39 +0100	[thread overview]
Message-ID: <87vbo4dmto.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <871tqsjh5x.fsf@gmx.us> (rasmus@gmx.us's message of "Wed, 1 Oct 2014 11:03:22 +0200")

Rasmus <rasmus@gmx.us> writes:

> Hi Phillip,
>
> phillip.lord@newcastle.ac.uk (Phillip Lord) writes:
>
> I might be misunderstanding your question here, so bear(?) with me.
>
> I think #+INCLUDE: "$FILE" should take care of what you want.
> Basically, at export time, INCLUDE is expanded to the content of $FILE
> in the buffer.  Footnotes should work.

So

master.org
  include  file1.org
  include  file2.org

Now, in file1.org add a footnote gets --

 [fn:1]


* Footnote

[fn:1] Footnote one


In file2.org add a footnote gets

 [fn:1]

* Foonote
 [fn:1] Footnote two

And footnote two gets lost.



I have a similar problem with hyperlinks. The normal store link
remembers the input.org file that the link is too. So, if in the
example, above I like between file2.org and file1.org using the Store
Link menu item, the HTML is wrong (since there is no file2.html
generated).

With latex and reftex, to put in a crossref, reftex knows about the
document structure and puts the hyperlink in as an internal reference,
since it will be internal when generated.

Phil

next prev parent reply	other threads:[~2014-10-01 11:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01  8:54 Multi-file and master files Phillip Lord
2014-10-01  9:03 ` Rasmus
2014-10-01 11:57   ` Phillip Lord [this message]
2014-10-01 12:26     ` Rasmus
2014-10-01 13:01       ` Phillip Lord
2014-10-01 13:27         ` Rasmus
2014-10-01 14:40           ` Phillip Lord
2014-10-01 14:56             ` Nicolas Goaziou
2014-10-01 15:44               ` Phillip Lord

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=87vbo4dmto.fsf@newcastle.ac.uk \
    --to=phillip.lord@newcastle.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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

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).