From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Understand the source of "Unable to resolve link" Date: Sun, 04 Feb 2018 15:58:15 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="089e0823d72008c80705646504b5" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38419) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eiMgV-0008QW-KK for emacs-orgmode@gnu.org; Sun, 04 Feb 2018 10:58:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eiMgU-0007q6-TU for emacs-orgmode@gnu.org; Sun, 04 Feb 2018 10:58:27 -0500 Received: from mail-yw0-x232.google.com ([2607:f8b0:4002:c05::232]:41528) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eiMgU-0007pu-Np for emacs-orgmode@gnu.org; Sun, 04 Feb 2018 10:58:26 -0500 Received: by mail-yw0-x232.google.com with SMTP id b129so16758055ywa.8 for ; Sun, 04 Feb 2018 07:58:26 -0800 (PST) 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: emacs-org list --089e0823d72008c80705646504b5 Content-Type: text/plain; charset="UTF-8" Hello, 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? Thanks. -- Kaushal Modi --089e0823d72008c80705646504b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

A user needs to support having gopher links in Org document:

=C2= =A0[[gopher://some.gopher.site][Dummy gopher link]]

But the ex= port fails saying that it's unable to resolve the link.

Th= e behavior can be easily recreated by exporting a document containing that = dummy link using C-c C-e h H.

I added "gopher" to th= e 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 fu= nction; I get:

=C2=A0=C2=A0=C2=A0 edebug-syntax-error: Invalid read = syntax: "Failed matching", (&rest (&define name (&res= t 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 el= sewhere?) so that gopher: protocol links are allowed?

Thanks.<= br>
--

Kaushal Modi

--089e0823d72008c80705646504b5--