From: ST <smntov@gmail.com>
To: Eric S Fraga <esflists@gmail.com>
Cc: Emacs-orgmode@gnu.org
Subject: Re: Structured links to headings with endless depth
Date: Mon, 12 Mar 2018 14:43:03 +0200 [thread overview]
Message-ID: <1520858583.1793.80.camel@gmail.com> (raw)
In-Reply-To: <87tvtlsi2f.fsf@gmail.com>
PS: It doesn't have to be Bible. Links in form of citations, like
[[MyBook:Chapter 1:Section 5:Subsection 3]]
Is quite useful in general. Where
#+LINK: MyBook path/to/MyBook.org::*%s
It is both readable as raw text and clickable.
Maybe it will be a good idea to be able to also add a <<target>> at the
end of the tree, like:
[[MyBook:Chapter 1:Section 5:Subsection 3:target]]
* Chapter 1
...
** Section 5
...
*** Subsection 3
...
<<target>>
...
-----------------------------
Adding an extra <<target>> is not an option, as it will make the text
less readable, and there is no need in this, as the headings tree
structure is already there:
* 1
** 1
** 2
*** 1
Why should I turn it into the following
* 1
** 1
** 2
*** 1
<<1>>
and then link with [[file:1]]?!... This both:
a) adds unnecessary information into the text making it less readable
b) those who read the org file as simple text without the ability to
click the link will not know where it goes... while the link
[[file:1:2:1]] makes it quite clear even without clicking it.
Example use case: scriptures with well known structure, e.g. the Bible.
On Mon, 2018-03-12 at 10:29 +0000, Eric S Fraga wrote:
> On Monday, 12 Mar 2018 at 12:09, ST wrote:
> > Hi,
> >
> > after reading the manual I didn't find a way to construct structured
> > links referring to headings with endless depth, like:
>
> I'm not entirely sure what your use case is but could you use a target,
> i.e. something like <<target>>, to indicate where you want to link to?
> Cf. section 4.2 of org manual on internal links.
>
prev parent reply other threads:[~2018-03-12 12:43 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
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 [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=1520858583.1793.80.camel@gmail.com \
--to=smntov@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=esflists@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).