From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Understand the source of "Unable to resolve link"
Date: Sun, 04 Feb 2018 17:19:02 +0100
Message-ID: <87k1vsiv7t.fsf@nicolasgoaziou.fr>
References: <CAFyQvY0zO4p5c15dNkknJvMeFYo9brzNVcwChX2VFMW9-t8f8A@mail.gmail.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 ([2001:4830:134:3::10]:43632)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1eiN0Y-0001Dp-CO
	for emacs-orgmode@gnu.org; Sun, 04 Feb 2018 11:19:11 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1eiN0U-0008O5-BT
	for emacs-orgmode@gnu.org; Sun, 04 Feb 2018 11:19:10 -0500
Received: from relay4-d.mail.gandi.net ([217.70.183.196]:58991)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <mail@nicolasgoaziou.fr>)
	id 1eiN0U-0008MR-4B
	for emacs-orgmode@gnu.org; Sun, 04 Feb 2018 11:19:06 -0500
In-Reply-To: <CAFyQvY0zO4p5c15dNkknJvMeFYo9brzNVcwChX2VFMW9-t8f8A@mail.gmail.com>
	(Kaushal Modi's message of "Sun, 04 Feb 2018 15:58:15 +0000")
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"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>

Hello,

Kaushal Modi <kaushal.modi@gmail.com> writes:

> A user needs to support having gopher links in Org document:
>
>  [[gopher://some.gopher.site][Dummy gopher link]]
>
> But the export fails saying that it's unable to resolve the link.
>
> The behavior can be easily recreated by exporting a document containing
> that dummy link using C-c C-e h H.
>
> I added "gopher" to the org-html-link function, but that obviously didn't
> help.
>
> I traced the error to org-export-data in ox.el, but I cannot edebug that
> function; I get:
>
>     edebug-syntax-error: Invalid read syntax: "Failed matching", (&rest
> (&define name (&rest arg) cl-declarations-or-string def-body))
>
> (I'll open an emacs bug for that.)
>
> So what needs to be fixed in ox.el (or elsewhere?) so that gopher: protocol
> links are allowed?

I don't think Org defines gopher links. Where is it registered? In
particular, what is the export function associated to the link type?

If you don't tell Org what it a gopher link, e.g., within
`org-link-parameters', Org considers your example above as a fuzzy link,
hence the error.

Regards,

-- 
Nicolas Goaziou