From mboxrd@z Thu Jan  1 00:00:00 1970
From: ST <smntov@gmail.com>
Subject: Re: Structured links to headings with endless depth
Date: Mon, 12 Mar 2018 12:39:50 +0200
Message-ID: <1520851190.1793.74.camel@gmail.com>
References: <1520849353.1793.66.camel@gmail.com> <87tvtlsi2f.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40873)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <smntov@gmail.com>) id 1evKs2-00019x-TW
	for Emacs-orgmode@gnu.org; Mon, 12 Mar 2018 06:39:59 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <smntov@gmail.com>) id 1evKrz-0002ZA-Qe
	for Emacs-orgmode@gnu.org; Mon, 12 Mar 2018 06:39:58 -0400
Received: from mail-wm0-x231.google.com ([2a00:1450:400c:c09::231]:38389)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <smntov@gmail.com>) id 1evKrz-0002Wo-KZ
	for Emacs-orgmode@gnu.org; Mon, 12 Mar 2018 06:39:55 -0400
Received: by mail-wm0-x231.google.com with SMTP id z9so15038617wmb.3
	for <Emacs-orgmode@gnu.org>; Mon, 12 Mar 2018 03:39:55 -0700 (PDT)
In-Reply-To: <87tvtlsi2f.fsf@gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Eric S Fraga <esflists@gmail.com>
Cc: Emacs-orgmode@gnu.org

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.
>