From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: #+LINK abbrevs possible in #+INCLUDEs ? Date: Mon, 27 Apr 2015 17:49:04 +0200 Message-ID: <874mo1bmhb.fsf@selenimh.mobile.lan> References: <20150427165913.76b92acc@gaia> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47675) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YmlG4-0000kk-3a for emacs-orgmode@gnu.org; Mon, 27 Apr 2015 11:47:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YmlG2-0006pt-S0 for emacs-orgmode@gnu.org; Mon, 27 Apr 2015 11:47:44 -0400 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:48113) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YmlG2-0006pl-KI for emacs-orgmode@gnu.org; Mon, 27 Apr 2015 11:47:42 -0400 In-Reply-To: <20150427165913.76b92acc@gaia> (Detlef Steuer's message of "Mon, 27 Apr 2015 16:59:13 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Detlef Steuer Cc: emacs-orgmode@gnu.org Hello, Detlef Steuer 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=C2=B4t 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=20 #+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, --=20 Nicolas Goaziou