From: Michael Brand <michael.ch.brand@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Eric S Fraga <esflists@gmail.com>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>,
org-mode-email <Emacs-orgmode@gnu.org>,
Christian Moe <mail@christianmoe.com>, ST <smntov@gmail.com>
Subject: Re: Structured links to headings with endless depth
Date: Wed, 14 Mar 2018 07:58:34 +0100 [thread overview]
Message-ID: <CALn3zoiFWaseAjZ862rMEPry=g0FWhyh4JbxFw3+7FRKPXD6UA@mail.gmail.com> (raw)
In-Reply-To: <CAJ51ETraHiyaaoFtC7gQnE-eUcu3zaYHt+wWgfgEymgDUu_vQQ@mail.gmail.com>
Hi John
On Wed, Mar 14, 2018 at 4:49 AM, John Kitchin <jkitchin@andrew.cmu.edu> wrote:
> (defun xpath-follow (path)
Thank you for this solution. I plan to adapt it to match the link path
only to a portion of a headline branch by ignoring the higher and
lower levels not given in the link path for my use case:
, (arbitrarily more levels upwards)
, * [...]
, * <composer>
, * <work>
, * TODO <movement>
, * <interpreter> :5:
, - The tag 5 is my rating of this audio recording.
, - The audio recording is stored under the file path
, [...]/<composer>/<work>/<movement>/<interpreter>/<sth>.mp3
,
, * TODO [...]
, - The theme is very similar to this prelude
, [[/:<composer_1>/<work_1>/<movement_1>]].
, * [...]
, - [...] like in this piano concert
, [[/:<composer_2>/<work_2>]].
Michael
next prev parent reply other threads:[~2018-03-14 6:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 10:09 Structured links to headings with endless depth ST
2018-03-12 10:29 ` Eric S Fraga
2018-03-12 10:39 ` ST
2018-03-12 13:08 ` Christian Moe
2018-03-12 13:46 ` ST
2018-03-12 14:10 ` Nicolas Goaziou
2018-03-12 15:08 ` ST
2018-03-14 3:49 ` John Kitchin
2018-03-14 6:58 ` Michael Brand [this message]
2019-05-06 16:34 ` Michael Brand
2019-05-07 3:26 ` Ihor Radchenko
2019-05-07 14:39 ` Michael Brand
2019-05-18 10:44 ` Ihor Radchenko
2018-03-14 10:10 ` ST
2018-03-14 13:26 ` Nicolas Goaziou
2018-03-14 18:11 ` ST
2018-03-14 18:32 ` Nicolas Goaziou
2018-03-14 18:46 ` ST
2018-03-14 14:15 ` John Kitchin
2018-03-14 18:07 ` ST
2018-03-12 12:43 ` ST
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='CALn3zoiFWaseAjZ862rMEPry=g0FWhyh4JbxFw3+7FRKPXD6UA@mail.gmail.com' \
--to=michael.ch.brand@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=esflists@gmail.com \
--cc=jkitchin@andrew.cmu.edu \
--cc=mail@christianmoe.com \
--cc=mail@nicolasgoaziou.fr \
--cc=smntov@gmail.com \
/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).