From: Samuel Wales <samologist@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [dev] Implement "ref" link types
Date: Sun, 19 Feb 2012 12:41:11 -0700 [thread overview]
Message-ID: <CAJcAo8uE5dKvMg4D7jCviTfJF6QjX90JYS+YDCaDJd79jWFX_A@mail.gmail.com> (raw)
In-Reply-To: <87vcn2vgq7.fsf@gmail.com>
I think it's a good idea, and would suggest this:
* If it is not going to have features added, then [[ref:asdf]] is OK
* If it /is/ going to have features added, then I recommend ES/US
ES/US is extensible syntax / universal syntax, a specific proposal for
an orthogonal and future-proof syntax for new capabilities like this.
For example, you might want to put the target anywhere, not just where
there are elements. The ID marker idea implements this with ES/US.
In this case, we'd simply allow element names in addition with the
same source syntax.
Of course, you might decide that nobody will ever want to add new
syntax to those links, in which case a simple new link type would make
sense.
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2012-02-19 19:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 18:08 [dev] Implement "ref" link types Nicolas Goaziou
2012-02-19 19:28 ` Christian Moe
2012-02-19 19:41 ` Nicolas Goaziou
2012-02-19 20:11 ` Toby Cubitt
2012-02-19 20:20 ` Christian Moe
2012-02-19 19:41 ` Samuel Wales [this message]
2012-02-19 20:02 ` Nicolas Goaziou
2012-02-19 20:48 ` Samuel Wales
2012-02-19 20:10 ` Carsten Dominik
2012-02-20 0:51 ` Nicolas Goaziou
2012-02-20 7:09 ` Carsten Dominik
2012-02-20 10:59 ` Nicolas Goaziou
2012-02-20 22:06 ` Nicolas Goaziou
2012-02-21 1:26 ` Thomas S. Dye
2012-02-21 5:14 ` David Maus
2012-02-21 9:18 ` Nicolas Goaziou
2012-02-27 19:38 ` Nicolas Goaziou
2012-02-27 20:38 ` David Maus
2012-03-05 9:37 ` Jambunathan K
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJcAo8uE5dKvMg4D7jCviTfJF6QjX90JYS+YDCaDJd79jWFX_A@mail.gmail.com \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.