From: ST <smntov@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Eric S Fraga <esflists@gmail.com>,
Emacs-orgmode@gnu.org, Christian Moe <mail@christianmoe.com>
Subject: Re: Structured links to headings with endless depth
Date: Mon, 12 Mar 2018 17:08:36 +0200 [thread overview]
Message-ID: <1520867316.1793.87.camel@gmail.com> (raw)
In-Reply-To: <87r2opcrkm.fsf@nicolasgoaziou.fr>
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 <smntov@gmail.com> 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,
>
next prev parent reply other threads:[~2018-03-12 15:08 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 [this message]
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
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=1520867316.1793.87.camel@gmail.com \
--to=smntov@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=esflists@gmail.com \
--cc=mail@christianmoe.com \
--cc=mail@nicolasgoaziou.fr \
/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).