From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: how to make relative file links?
Date: Tue, 05 Nov 2013 18:51:24 -0500 [thread overview]
Message-ID: <87bo1yz9tv.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 87d2meqz5q.fsf@pcbe13433.cern.ch
David Belohrad <david@belohrad.ch> writes:
> Dear all,
>
> i've just noticed one annoying thing. When I specify the relative file
> link by org-insert-link, then I specify 'file:' <enter>, then i specify
> filename with relative path, the function converts the relative path to
> absolute path. so when i move my org files into another location,
> well...
>
> is there any way how to tell to org-store-link (and as well to %a in
> org-capture templates) to specify link path relative to the file the
> link is stored in?
>
> respectively: if file contains many links, how can i assure file: links
> portability when entire org tree changes location?
>
> many thanks
>
> david
Does this help?
,----
| org-link-file-path-type is a variable defined in `org.el'.
| Its value is adaptive
|
| Documentation:
| How the path name in file links should be stored.
| Valid values are:
|
| relative Relative to the current directory, i.e. the directory of the file
| into which the link is being inserted.
| absolute Absolute path, if possible with ~ for home directory.
| noabbrev Absolute path, no abbreviation of home directory.
| adaptive Use relative path for files in the current directory and sub-
| directories of it. For other files, use an absolute path.
|
| You can customize this variable.
|
| [back]
`----
Nick
next prev parent reply other threads:[~2013-11-05 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 22:09 how to make relative file links? David Belohrad
2013-11-05 23:51 ` Nick Dokos [this message]
2013-11-06 7:52 ` David Belohrad
2013-11-20 3:18 ` Samuel Wales
2013-11-20 3:48 ` Nick Dokos
2013-11-20 4:27 ` Samuel Wales
2013-11-06 7:57 ` David Belohrad
2013-11-06 8:43 ` paul-sqPYmOVXOov10XsdtD+oqA
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=87bo1yz9tv.fsf@alphaville.bos.redhat.com \
--to=ndokos@gmail.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).