From mboxrd@z Thu Jan 1 00:00:00 1970 From: ST Subject: Re: Structured links to headings with endless depth Date: Mon, 12 Mar 2018 17:08:36 +0200 Message-ID: <1520867316.1793.87.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> 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]:49247) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evP4A-0001BE-8J for Emacs-orgmode@gnu.org; Mon, 12 Mar 2018 11:08:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1evP46-0000M0-95 for Emacs-orgmode@gnu.org; Mon, 12 Mar 2018 11:08:46 -0400 Received: from mail-wm0-x229.google.com ([2a00:1450:400c:c09::229]:54778) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1evP46-0000LH-2H for Emacs-orgmode@gnu.org; Mon, 12 Mar 2018 11:08:42 -0400 Received: by mail-wm0-x229.google.com with SMTP id z81so17212612wmb.4 for ; Mon, 12 Mar 2018 08:08:42 -0700 (PDT) In-Reply-To: <87r2opcrkm.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 , Emacs-orgmode@gnu.org, Christian Moe Hello, Ss Christian has pointed out - introduce a separate CUSTOM_ID for text with fixed structure and rather short verses is too heavy. I do need to write a custom link type, if this use case is not of common interest for the orgmode community. Thank you, On Mon, 2018-03-12 at 15:10 +0100, Nicolas Goaziou wrote: > Hello, > > ST writes: > > > I'm not that experienced in writing in lisp. Is it difficult to create > > such custom link type? What is the closest link type that you would > > recommend to take as starting point (link on code, if possible)? > > I'm not answering your question, but I suggest to use a CUSTOM_ID > instead. This is readily available. > > Regards, >