From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Detlef Steuer <detlef.steuer@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: #+LINK abbrevs possible in #+INCLUDEs ?
Date: Mon, 27 Apr 2015 17:49:04 +0200 [thread overview]
Message-ID: <874mo1bmhb.fsf@selenimh.mobile.lan> (raw)
In-Reply-To: <20150427165913.76b92acc@gaia> (Detlef Steuer's message of "Mon, 27 Apr 2015 16:59:13 +0200")
Hello,
Detlef Steuer <detlef.steuer@gmx.de> writes:
> I have two files:
>
> file1.org:
> --------------------
> #+LINK: HOME http://example.de
>
> * My Homepage You can find my homepage [[HOME][here]]
>
> #+INCLUDE: file2.org
> --------------------
>
> file2.org --------------------
> #+LINK: HOME2 http://other.example.de
>
> * My other page
> You can find my other page [[HOME2][here]]
> --------------------
>
> I can export file2.org to html as expected.
>
> I can´t export file1.org to html with the included file2.org.
> Only if I move the #+LINK line from file2 to file1 the export
> works as expected.
>
> In my setting file2.org must export standalone, so moving the LINKs to
> file1 is no option. An ugly workaround would be to include the
> abbreviation for HOME2 in both files. Ugly.
>
> Is there a woraround/setting to have local #+LINK directives working in
> included files?
You can extract out #+LINK: keywords in a file, e.g. "setup.org" and
use #+SETUPFILE: ... in both "file1.org" and "file2.org".
You can also use
#+SETUPFILE: file2.org
in "file1.org".
Set-up (e.g., link abbreviations) is not refreshed after expanding
INCLUDE keywords. I cannot remember why, tho. Maybe for (dubious)
efficiency reasons.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-04-27 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 14:59 #+LINK abbrevs possible in #+INCLUDEs ? Detlef Steuer
2015-04-27 15:49 ` Nicolas Goaziou [this message]
2015-04-27 17:55 ` Detlef Steuer
2015-04-27 18:46 ` Nicolas Goaziou
2015-04-28 15:02 ` Detlef Steuer
2015-04-29 11:42 ` Alan Schmitt
2015-04-29 15:05 ` Nicolas Goaziou
2015-04-30 11:30 ` Alan Schmitt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mo1bmhb.fsf@selenimh.mobile.lan \
--to=mail@nicolasgoaziou.fr \
--cc=detlef.steuer@gmx.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.