From mboxrd@z Thu Jan 1 00:00:00 1970 From: Detlef Steuer Subject: Re: #+LINK abbrevs possible in #+INCLUDEs ? Date: Mon, 27 Apr 2015 19:55:42 +0200 Message-ID: <20150427195542.6f7ecdff@linux-w3xx.localdomain> References: <20150427165913.76b92acc@gaia> <874mo1bmhb.fsf@selenimh.mobile.lan> 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]:60777) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YmnG1-0002mt-RL for emacs-orgmode@gnu.org; Mon, 27 Apr 2015 13:55:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YmnFy-0006jR-Gz for emacs-orgmode@gnu.org; Mon, 27 Apr 2015 13:55:49 -0400 Received: from mout.gmx.net ([212.227.15.18]:51768) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YmnFy-0006ir-7Y for emacs-orgmode@gnu.org; Mon, 27 Apr 2015 13:55:46 -0400 In-Reply-To: <874mo1bmhb.fsf@selenimh.mobile.lan> 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: emacs-orgmode@gnu.org > Hello, >=20 > Detlef Steuer writes: >=20 > > 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? >=20 > 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. >=20 > You can also use=20 >=20 > #+SETUPFILE: file2.org >=20 > 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. >=20 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!=20 Thank you for the hints! Regards Detlef >=20 > Regards, >=20