From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: [dev] Implement "ref" link types
Date: Sun, 19 Feb 2012 20:41:45 +0100
Message-ID: <87r4xqvcee.fsf@gmail.com>
References: <87vcn2vgq7.fsf@gmail.com> <4F414D57.5090205@christianmoe.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:37330)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1RzCf5-0001Vf-PZ
	for emacs-orgmode@gnu.org; Sun, 19 Feb 2012 14:43:08 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1RzCf4-0004D9-Ji
	for emacs-orgmode@gnu.org; Sun, 19 Feb 2012 14:43:07 -0500
Received: from mail-we0-f169.google.com ([74.125.82.169]:34894)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1RzCf4-0004D5-Dz
	for emacs-orgmode@gnu.org; Sun, 19 Feb 2012 14:43:06 -0500
Received: by wera13 with SMTP id a13so3632100wer.0
	for <emacs-orgmode@gnu.org>; Sun, 19 Feb 2012 11:43:05 -0800 (PST)
In-Reply-To: <4F414D57.5090205@christianmoe.com> (Christian Moe's message of
	"Sun, 19 Feb 2012 20:28:23 +0100")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: mail@christianmoe.com
Cc: Org Mode List <emacs-orgmode@gnu.org>

Hello,

Christian Moe <mail@christianmoe.com> writes:

> Me, I don't see any problem with a [[ref:something]] syntax. It's the
> obvious org-native, cross-backend replacement for \ref. The
> [[protocol:something]] syntax already widens the notion of link to
> shell: and elisp: links, so I wouldn't worry about breaking
> conventions. Using e.g. [[!something]] instead would introduce a brand
> new bit of syntax.

Not really brand new, since there already are [[#custom-id]] and
[[*headline]].  Though, I'd favour [[ref:name]], too.

> Suggestion: On export, how about enabling automatic element
> descriptions for references following the type:name convention, so
> that e.g. just
>
> : in [[ref:tab:numbers]] we can see...
>
> would expand to
>
>   in Table 2 we can see...
>
> If implemented, this should be user-customizable e.g. through an alist
> like
>
>   (("fig" . "Figure") ("tab" . "Table") ("map" . "Map"))

That's another possibility, but I'd rather follow LaTeX usage. I think
it gives user more latitude in the end. Indeed, You don't have to think
about a name prefix ; you can also have constructs like "Tables
[[ref:table1]], [[ref:table2]] and [[ref:table3]]" for "Tables 1, 2 and
3", etc.

Note that the behaviour you suggest can easily be implemented using
filters in the new exporter.


Regards,

-- 
Nicolas Goaziou