From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe Subject: Re: Structured links to headings with endless depth Date: Mon, 12 Mar 2018 14:08:37 +0100 Message-ID: <87lgexfnl6.fsf@christianmoe.com> References: <1520849353.1793.66.camel@gmail.com> <87tvtlsi2f.fsf@gmail.com> <1520851190.1793.74.camel@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47259) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evNC3-0004Gv-CP for Emacs-orgmode@gnu.org; Mon, 12 Mar 2018 09:08:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1evNBx-0006uo-HJ for Emacs-orgmode@gnu.org; Mon, 12 Mar 2018 09:08:47 -0400 Received: from mailer-211-152.hitrost.net ([91.185.211.152]:41060) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1evNBx-0006oD-AF for Emacs-orgmode@gnu.org; Mon, 12 Mar 2018 09:08:41 -0400 In-reply-to: <1520851190.1793.74.camel@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: ST Cc: Eric S Fraga , Emacs-orgmode@gnu.org ST writes: > Adding an extra <> 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: Adding targets, CUSTOM_IDs or IDs are all options. You may not like them. > * 1 > ** 1 > ** 2 > *** 1 > > Why should I turn it into the following > > * 1 > ** 1 > ** 2 > *** 1 > <<1>> With a fixed structure, you wouldn't; you'd use e.g. <<1:2:1>>. > and then link with [[file:1]]?!... This both: > a) adds unnecessary information into the text making it less readable Let's not exaggerate the readability cost. And it does add information. > 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. But so does the link [[1:2:1]] to the target <<1:2:1>>. also, c): Adding a target like <<1:2:1>> to a section preserves information about the location of that section in the source document if you later cut that part out and insert it somewhere else. This information is not contained in your headlines. > Example use case: scriptures with well known structure, e.g. the Bible. Fair enough. But typical Org use will quickly break links like that, since Org shines as an organizer for drafting and easily restructuring text. I don't think Org needs a link type that would encourage people to make easily breakable links. I acknowledge that a separate target or CUSTOM_ID for every verse in the Bible seems a bit heavy; if that's what you need, it might be better solved by a custom link type. Yours, Christian > > 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 <>, to indicate where you want to link to? >> Cf. section 4.2 of org manual on internal links. >>