From: Bastien <firstname.lastname@example.org>
To: "D. C. Toedt" <email@example.com>
Subject: Re: External link abbreviations don't work when contained in #+INCLUDE file
Date: Tue, 01 May 2012 13:30:23 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <CAGN11+0TOQtni5D=FHr_jdQgMYWYpxCmj0XOZOmSsVKMMN1t5w@mail.gmail.com> (D. C. Toedt's message of "Mon, 30 Apr 2012 11:04:27 -0500")
"D. C. Toedt" <email@example.com> writes:
> External link abbreviations don't seem to work if they're in an #
> +INCLUDE file -- they end up pointing to a (non-existent) anchor
> within the main document.
> The same external link abbreviations seem to work fine if they're in
> the main file.
That's the thing to do: put the links abbreviations in the main file or
in `org-link-abbrev-alist'. Options are local to the file and it would
be inconsistent to make an exception for #+LINK.
prev parent reply other threads:[~2012-05-01 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 16:04 External link abbreviations don't work when contained in #+INCLUDE file D. C. Toedt
2012-05-01 11:30 ` Bastien [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).