David Belohrad <da...@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
