Re: [O] Parent path for links

Christian Wittern wrote: [...] > Look at Section 4.6 Link Abbreviations in the manual. What you would want > to do is having > > #+LINK: wp ~/working/project > > in your header, than you can reference it as [[wp:your-project.org]] instead > of [[~/working/project/your-project.org]]. Ahh... neat.

Re: [O] Parent path for links

On 2015-02-19 10:55, Giacomo M wrote: > What happens is that in project.org I end up specifying > a lot of links all starting with ~/working/project/. This is useful as I can > directly jump from "organization" to "action", or just to switch in a > quicker way across project fi

Re: [O] Parent path for links

Giacomo M wrote: [...] > What happens is that in project.org I end up specifying a lot of links all > starting with ~/working/project/. This is useful as I can directly jump > from "organization" to "action", or just to switch in a quicker way across > project files. [...] > Would you have any sug

[O] Parent path for links

Dear all, I'm experimenting the following path structure: 1. ~/org/ is where I keep all my org files for organization purposes (e.g. project.org contains all TODOs, notes, events, and links related to "project") and is sync'd with a GIT server. 2. ~/working/project/ is where I keep all the non-or