emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: FR: broken links and footnote references
Date: Thu, 24 Mar 2011 01:06:17 -0700	[thread overview]
Message-ID: <AANLkTinwiSO=N40HTiWmzTR5cA31zVyoqB_+Vg3UP4J6@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikrFhWiUaseD8G0UgkQpPNJzN3_v0D0zRA_2CF-@mail.gmail.com>

Not sure if this thread was clear enough to make it interesting.

I am suggesting that when you export a subtree or a region, and you
have a link to an anchor (e.g. a link to a <<...>>>), and that link is
broken, because the referent is outside of the subtree or region, we
can do this:

  Get the link referent normally (just as we do in the .org file)
  Append it to a URL provided in a property for the subtree that contains it

That way, you can export one subtree as a blog entry, and another
subtree as a blog entry, and if links point to the other subtree, they
will get exported properly -- as long as you supply the base URL.

      reply	other threads:[~2011-03-24  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 18:48 FR: broken links and footnote references Samuel Wales
2011-03-14  3:02 ` Samuel Wales
2011-03-24  8:06   ` Samuel Wales [this message]

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:

  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='AANLkTinwiSO=N40HTiWmzTR5cA31zVyoqB_+Vg3UP4J6@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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).