From mboxrd@z Thu Jan 1 00:00:00 1970 From: ST Subject: Re: Structured links to headings with endless depth Date: Wed, 14 Mar 2018 20:11:55 +0200 Message-ID: <1521051115.1930.108.camel@gmail.com> References: <1520849353.1793.66.camel@gmail.com> <87tvtlsi2f.fsf@gmail.com> <1520851190.1793.74.camel@gmail.com> <87lgexfnl6.fsf@christianmoe.com> <1520862394.1793.83.camel@gmail.com> <87r2opcrkm.fsf@nicolasgoaziou.fr> <1520867316.1793.87.camel@gmail.com> <1521022248.1930.85.camel@gmail.com> <87h8pin5yq.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44867) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ewAsg-0005Wf-5X for Emacs-orgmode@gnu.org; Wed, 14 Mar 2018 14:12:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ewAsc-00031w-4R for Emacs-orgmode@gnu.org; Wed, 14 Mar 2018 14:12:06 -0400 Received: from mail-wr0-x230.google.com ([2a00:1450:400c:c0c::230]:35132) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ewAsb-00031d-Tm for Emacs-orgmode@gnu.org; Wed, 14 Mar 2018 14:12:02 -0400 Received: by mail-wr0-x230.google.com with SMTP id n12so5745383wra.2 for ; Wed, 14 Mar 2018 11:12:01 -0700 (PDT) In-Reply-To: <87h8pin5yq.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou Cc: Eric S Fraga , org-mode-email , Christian Moe , John Kitchin On Wed, 2018-03-14 at 14:26 +0100, Nicolas Goaziou wrote: > Hello, > > > I think this kind of linking is useful for many general cases. Christian > > has expressed concerns that such links are easily breakable which is > > true but only for documents that are in draft phase (or those which are > > supposed to be restructured on regular basis - like ToDo lists). However > > documents that has been published, like books or scientific papers, and > > will no longer change - will benefit greatly from such linking option. > > Imagine you have a scientific paper in your archive that you have > > already published and removed write access from it in order not to > > change it accidentally. You do want to reference certain > > chapter:section:subsection from it in your new paper, which you are > > currently writing, but creating a target <> > > in the old paper is no longer an option... > > > > So may I ask as a feature request, to please add, following link type as > > standard to the org-mode: > > > > [[path/to/file.org::chapter:section:subsection:etc:optional target]] > > > > - chapter/section/subsection could be also just numbers > > - optional target target might be <> > > - there is no need to add '*' (like > > [[path/to/file.org::*chapter:section]] to the link, as ':' after '::' > > imply that headings are referred. > > > > Thank you! > > Again, even in the case you are talking about, CUSTOM_ID is better, for > at least two reasons: > - it leads to much simpler links: [[file.org::#my-id]] Why [[file.org::#1:2:1]] is nicer than [file.org::1:2:1]]? > - it translates nicely to "id" tag in HTML. You can generate the "id" tag in HTML like this 1-2-1 (if HTML dislikes 1:2:1 tag) > > I understand this was not so useful in your use case (only headlines, no > contents), but, it is still valid as a general mechanism. Isn't a good idea to add such a built in link type in the long term? Thank you!