From: Michael Brand <michael.ch.brand@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: outline path in links
Date: Wed, 6 Apr 2011 19:24:15 +0200 [thread overview]
Message-ID: <BANLkTi=FzusDgaKvt8RnXcPLH0uVHo6eSA@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimLucDWOvnEBVtNs4UxR4K-wfR63jtvma7bn4f2@mail.gmail.com>
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 <michael.ch.brand@gmail.com> 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.
prev parent reply other threads:[~2011-04-06 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 18:18 outline path in links Michael Brand
2011-04-06 17:24 ` Michael Brand [this message]
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='BANLkTi=FzusDgaKvt8RnXcPLH0uVHo6eSA@mail.gmail.com' \
--to=michael.ch.brand@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).