On Sun, Feb 4, 2018 at 11:31 AM Nicolas Goaziou
wrote:
> Note that you cannot simply copy "http" or "https" types. As default
> type links, they are hard-coded in every export back-end. It means they
> do not have to set any :export property.
>
> As a user, if you want to export a "gopher" link t
Kaushal Modi writes:
> Thanks. I'll ask the user to update that variable (or can that be updated
> in the default value?).
Note that you cannot simply copy "http" or "https" types. As default
type links, they are hard-coded in every export back-end. It means they
do not have to set any :export p
On Sun, Feb 4, 2018 at 11:19 AM Nicolas Goaziou
wrote:
> Hello,
>
> I don't think Org defines gopher links. Where is it registered? In
> particular, what is the export function associated to the link type
Looks like[1], gopher: links can behave the same way as https:, http:, etc.
If you don't
Hello,
Kaushal Modi 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
> tha
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 a
