From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: Re: outline path in links Date: Wed, 6 Apr 2011 19:24:15 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from [140.186.70.92] (port=49646 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q7WSu-00025u-00 for emacs-orgmode@gnu.org; Wed, 06 Apr 2011 13:24:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q7WSp-0000Yf-N1 for emacs-orgmode@gnu.org; Wed, 06 Apr 2011 13:24:23 -0400 Received: from mail-iw0-f169.google.com ([209.85.214.169]:62074) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q7WSp-0000YM-Jw for emacs-orgmode@gnu.org; Wed, 06 Apr 2011 13:24:19 -0400 Received: by iwg8 with SMTP id 8so2215407iwg.0 for ; Wed, 06 Apr 2011 10:24:16 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org Mode Hi all In the meantime I realized that for a good stability of the document consistency it is a rather bad idea to have the name of a parent heading like `Bach' to be part of the key to the item `Prelude' for the [[*Bach/Prelude]] link mentioned earlier. Therefore I will instead use :ID: links with the automatically inserted UUID (see `C-h v org-link-to-org-use-id RET'). Thanks a lot for :ID: links. Michael On Thu, Jan 13, 2011 at 19:18, Michael Brand wrote: > Hi all > > What do you think about having _outline path in links_ as described in > the following? > > I have seen that an outline path like `Bach/Prelude' can be used to > refile notes into a heading `Prelude' that has a parent heading named > `Bach'. An outline path like `Chopin/Prelude' refiles into a different > heading with the same name `Prelude' but with a different parent > heading named `Chopin'. > > Now I wondered if the link type [[*Bach/Prelude]] could be used to > _link_ to the first outline path above. This link type would be even > _plainer plain text_ and easier to add to a Org buffer than the link > type [[#Bach/Prelude]] because the latter requires to manually add the > property `:CUSTOM_ID: Bach/Prelude' > > I think that such an outline path in links could be possible even > without the need of adding a new variable org-link-use-outline-path > similar to the existing variable org-refile-use-outline-path: Like > today the link [[*Orchestersuite/Ouverture]] would still match a > heading named `Orchestersuite/Ouverture' (both words on the same > heading level with a literal slash as part of the heading name) but > additionally the link [[*Bach/Orchestersuite/Ouverture]] then would > match this heading only if it has a parent heading named `Bach'. This > would not be the simplest way to implement but in my opinion the > priority should be to have as less config variables as possible. Even > better if the code that gives this flexibility could also be used for > refiling with outline path and the variable > org-refile-use-outline-path could be dropped.