From: Pavel Panchekha <me@pavpanchekha.com>
To: emacs-orgmode@gnu.org
Subject: Relative links and #+include:
Date: Mon, 27 Jul 2015 22:36:13 -0700 [thread overview]
Message-ID: <1438061773.1354.1@smtp.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
I create the RSS feed for my blog with a file that #+include:'s the
various blog posts; this way, when I export it to RSS using ox-rss.el,
the full text of each blog post is in the feed. The feed is generated
from a file called "/rss.org", and the blog posts themselves are
located in "/blog/*.org".
I've noticed that when a post has a relative link to another post,
images, or source code, that link is broken. For example, when a post
in "/blog/zippers/huet.org" links to "kiselyov.org", which should be a
link to the page "/blog/zippers/kiselyov.org", the link is instead
interpreted as a link to "/kiselyov.org", since the post is being
#+include:'d into a file in "/".
Is there any way to advise the #+include: process to resolve relative
links correctly? Or a better way to include Org files in one another?
—Pavel Panchekha
[-- Attachment #2: Type: text/html, Size: 926 bytes --]
next reply other threads:[~2015-07-28 5:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 5:36 Pavel Panchekha [this message]
2015-07-28 8:43 ` Relative links and #+include: Rasmus
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=1438061773.1354.1@smtp.gmail.com \
--to=me@pavpanchekha.com \
--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).