From: Detlef Steuer <detlef.steuer@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: #+LINK abbrevs possible in #+INCLUDEs ?
Date: Mon, 27 Apr 2015 19:55:42 +0200 [thread overview]
Message-ID: <20150427195542.6f7ecdff@linux-w3xx.localdomain> (raw)
In-Reply-To: <874mo1bmhb.fsf@selenimh.mobile.lan>
> 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".
OK, but still this is kind of ugly, because the LINKs really are file
specific for ,- in the long run -, multiple files.
>
> You can also use
>
> #+SETUPFILE: file2.org
>
> in "file1.org".
>
The real file2.org is somewhat big and would be scanned completely,
wouldn't it?
> Set-up (e.g., link abbreviations) is not refreshed after expanding
> INCLUDE keywords. I cannot remember why, tho. Maybe for (dubious)
> efficiency reasons.
>
If you don't remember, may be it would be possible to try it out?
Would love it and as a feature it looks natural for an included file!
Thank you for the hints!
Regards
Detlef
>
> Regards,
>
next prev parent reply other threads:[~2015-04-27 17:55 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
2015-04-27 17:55 ` Detlef Steuer [this message]
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
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=20150427195542.6f7ecdff@linux-w3xx.localdomain \
--to=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 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).