emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Understand the source of "Unable to resolve link"
Date: Sun, 04 Feb 2018 17:19:02 +0100	[thread overview]
Message-ID: <87k1vsiv7t.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY0zO4p5c15dNkknJvMeFYo9brzNVcwChX2VFMW9-t8f8A@mail.gmail.com> (Kaushal Modi's message of "Sun, 04 Feb 2018 15:58:15 +0000")

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

next prev parent reply	other threads:[~2018-02-04 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04 15:58 Understand the source of "Unable to resolve link" Kaushal Modi
2018-02-04 16:19 ` Nicolas Goaziou [this message]
2018-02-04 16:23   ` Kaushal Modi
2018-02-04 16:31     ` Nicolas Goaziou
2018-02-04 20:42       ` Kaushal Modi

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=87k1vsiv7t.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@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

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).