From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: outline path in links Date: Thu, 13 Jan 2011 19:18:21 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from [140.186.70.92] (port=51146 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PdRkd-0007vl-TS for emacs-orgmode@gnu.org; Thu, 13 Jan 2011 13:18:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PdRkc-0001Q3-Cc for emacs-orgmode@gnu.org; Thu, 13 Jan 2011 13:18:23 -0500 Received: from mail-iw0-f169.google.com ([209.85.214.169]:38965) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PdRkc-0001Pz-7I for emacs-orgmode@gnu.org; Thu, 13 Jan 2011 13:18:22 -0500 Received: by iwn40 with SMTP id 40so1961765iwn.0 for ; Thu, 13 Jan 2011 10:18:21 -0800 (PST) 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 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. Michael