From mboxrd@z Thu Jan 1 00:00:00 1970 From: Skip Collins Subject: non-standard link errors Date: Fri, 26 Feb 2016 13:25:26 -0500 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55991) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZN5H-0006hp-S8 for emacs-orgmode@gnu.org; Fri, 26 Feb 2016 13:25:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aZN5H-0003o2-48 for emacs-orgmode@gnu.org; Fri, 26 Feb 2016 13:25:47 -0500 Received: from mail-qg0-x233.google.com ([2607:f8b0:400d:c04::233]:33657) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZN5G-0003nq-KY for emacs-orgmode@gnu.org; Fri, 26 Feb 2016 13:25:46 -0500 Received: by mail-qg0-x233.google.com with SMTP id d32so15816664qgd.0 for ; Fri, 26 Feb 2016 10:25:46 -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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-org list Org throws an error when I export html with a link type that it does not know about. I would like it to simply add the link to the exported document without checking its validity. For example, I have a link that, when tapped on an iPhone, will open a particular app. I would like the html to look something like: Connect using FaceTime The link works on an iPhone. But Org won't generate the html. Other apps uses x-callback-url links formatted like this: x-appname://x-callback-url/import?&description=Open%20Mail.app..... These also do not work. Short of adding every type I might want to use with org-add-link-type, is it possible to disable the export error and just pass links through as written? From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: non-standard link errors Date: Fri, 26 Feb 2016 22:56:09 +0100 Message-ID: <87vb5bdtl2.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58475) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZQKx-0004US-7Q for emacs-orgmode@gnu.org; Fri, 26 Feb 2016 16:54:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aZQKs-0000DU-8U for emacs-orgmode@gnu.org; Fri, 26 Feb 2016 16:54:11 -0500 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:51044) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZQKs-0000DJ-1u for emacs-orgmode@gnu.org; Fri, 26 Feb 2016 16:54:06 -0500 In-Reply-To: (Skip Collins's message of "Fri, 26 Feb 2016 13:25:26 -0500") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Skip Collins Cc: emacs-org list Hello, Skip Collins writes: > Org throws an error when I export html with a link type that it does > not know about. I would like it to simply add the link to the exported > document without checking its validity. For example, I have a link > that, when tapped on an iPhone, will open a particular app. I would > like the html to look something like: > Connect using FaceTime > > The link works on an iPhone. But Org won't generate the html. Other > apps uses x-callback-url links formatted like this: > x-appname://x-callback-url/import?&description=Open%20Mail.app..... > > These also do not work. Short of adding every type I might want to use > with org-add-link-type, is it possible to disable the export error and > just pass links through as written? It is possible in development version, where a variable controlling how link errors should be handled was introduced. Regards, -- Nicolas Goaziou From mboxrd@z Thu Jan 1 00:00:00 1970 From: Skip Collins Subject: Re: non-standard link errors Date: Sat, 27 Feb 2016 13:23:40 -0500 Message-ID: References: <87vb5bdtl2.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51856) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZjX7-00049I-BD for emacs-orgmode@gnu.org; Sat, 27 Feb 2016 13:24:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aZjX6-0006r0-Fw for emacs-orgmode@gnu.org; Sat, 27 Feb 2016 13:24:01 -0500 Received: from mail-qk0-x234.google.com ([2607:f8b0:400d:c09::234]:36801) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZjX6-0006qv-BZ for emacs-orgmode@gnu.org; Sat, 27 Feb 2016 13:24:00 -0500 Received: by mail-qk0-x234.google.com with SMTP id s68so43163902qkh.3 for ; Sat, 27 Feb 2016 10:24:00 -0800 (PST) In-Reply-To: <87vb5bdtl2.fsf@nicolasgoaziou.fr> 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-org list Nicolas Goaziou wrote: > Skip Collins writes: > > Org throws an error when I export html with a link type that it does > > not know about. I would like it to simply add the link to the exported > > document without checking its validity. For example, I have a link > > that, when tapped on an iPhone, will open a particular app. I would > > like the html to look something like: > > Connect using FaceTime > > > > The link works on an iPhone. But Org won't generate the html. Other > > apps uses x-callback-url links formatted like this: > > x-appname://x-callback-url/import?&description=Open%20Mail.app..... > > > > These also do not work. Short of adding every type I might want to use > > with org-add-link-type, is it possible to disable the export error and > > just pass links through as written? > > It is possible in development version, where a variable controlling how > link errors should be handled was introduced. I added this line to the top of my org file: #+OPTIONS: broken-links:t But that eliminates both the link and its description from the export. Changing it from 't' to 'mark' puts a BROKEN LINK message in the output. I suggest adding a new option 'pass' that would simply pass "broken" links verbatim into the output. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: non-standard link errors Date: Sun, 28 Feb 2016 09:28:53 +0100 Message-ID: <874mctck6y.fsf@nicolasgoaziou.fr> References: <87vb5bdtl2.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47925) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZwgl-00009o-A3 for emacs-orgmode@gnu.org; Sun, 28 Feb 2016 03:26:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aZwgk-0001bM-9u for emacs-orgmode@gnu.org; Sun, 28 Feb 2016 03:26:51 -0500 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:35300) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZwgk-0001bG-4G for emacs-orgmode@gnu.org; Sun, 28 Feb 2016 03:26:50 -0500 In-Reply-To: (Skip Collins's message of "Sat, 27 Feb 2016 13:23:40 -0500") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Skip Collins Cc: emacs-org list Hello, Skip Collins writes: > I added this line to the top of my org file: > #+OPTIONS: broken-links:t > > But that eliminates both the link and its description from the export. > Changing it from 't' to 'mark' puts a BROKEN LINK message in the > output. I suggest adding a new option 'pass' that would simply pass > "broken" links verbatim into the output. Not that I'm against the idea, but wouldn't it be a poor way to properly fix the issue, i.e., add new link types? Regards, -- Nicolas Goaziou From mboxrd@z Thu Jan 1 00:00:00 1970 From: Skip Collins Subject: Re: non-standard link errors Date: Sun, 28 Feb 2016 23:04:24 -0500 Message-ID: References: <87vb5bdtl2.fsf@nicolasgoaziou.fr> <874mctck6y.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50397) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaF4f-00011m-H2 for emacs-orgmode@gnu.org; Sun, 28 Feb 2016 23:04:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aaF4e-00034I-KK for emacs-orgmode@gnu.org; Sun, 28 Feb 2016 23:04:45 -0500 Received: from mail-qg0-x22e.google.com ([2607:f8b0:400d:c04::22e]:33614) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaF4e-000346-G5 for emacs-orgmode@gnu.org; Sun, 28 Feb 2016 23:04:44 -0500 Received: by mail-qg0-x22e.google.com with SMTP id d32so51318720qgd.0 for ; Sun, 28 Feb 2016 20:04:44 -0800 (PST) In-Reply-To: <874mctck6y.fsf@nicolasgoaziou.fr> 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-org list Nicolas Goaziou wrote: > Not that I'm against the idea, but wouldn't it be a poor way to properly > fix the issue, i.e., add new link types? I have come up with a better solution than globally passing "broken" links. I defined a new "raw" link type. So now if I want to put a non-standard link in my export, I can do something like: Here is a [[raw:foo:/\bar, baz][bad link]]. which is exported in html as: Here is a bad link. Now I can have non-standard links included in the output without disabling link checking for all standard link types. This is how it is defined in my .emacs: (org-add-link-type "raw" 'org-raw-follow 'org-raw-export) (defun org-raw-follow (path)) (defun org-raw-export (path desc format) "Export a raw link. See `org-add-link-type' for details about PATH, DESC and FORMAT." (cond ((eq format 'html) (format "%s" path desc)) ((eq format 'latex) (format "\\href{%s}{%s}" path desc)) ((eq format 'ascii) (format "%s (%s)" desc path)) (t path))) Perhaps this could be included in the standard Org distribution as a fallback option for exporting non-standard link types. Emacs/Org does nothing with the link. The user is responsible for ensuring the output is correct. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: non-standard link errors Date: Mon, 29 Feb 2016 19:10:34 +0100 Message-ID: <87wppnz8th.fsf@nicolasgoaziou.fr> References: <87vb5bdtl2.fsf@nicolasgoaziou.fr> <874mctck6y.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51629) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaSFI-0003Kd-4s for emacs-orgmode@gnu.org; Mon, 29 Feb 2016 13:08:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aaSFD-0008Ql-1o for emacs-orgmode@gnu.org; Mon, 29 Feb 2016 13:08:36 -0500 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:35729) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaSFC-0008QZ-N2 for emacs-orgmode@gnu.org; Mon, 29 Feb 2016 13:08:30 -0500 In-Reply-To: (Skip Collins's message of "Sun, 28 Feb 2016 23:04:24 -0500") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Skip Collins Cc: emacs-org list Hello, Skip Collins writes: > I have come up with a better solution than globally passing "broken" > links. I defined a new "raw" link type. So now if I want to put a > non-standard link in my export, I can do something like: > Here is a [[raw:foo:/\bar, baz][bad link]]. > which is exported in html as: > Here is a bad link. > > Now I can have non-standard links included in the output without > disabling link checking for all standard link types. This is how it is > defined in my .emacs: > (org-add-link-type "raw" 'org-raw-follow 'org-raw-export) > (defun org-raw-follow (path)) > (defun org-raw-export (path desc format) > "Export a raw link. > See `org-add-link-type' for details about PATH, DESC and FORMAT." > (cond > ((eq format 'html) (format "%s" path desc)) > ((eq format 'latex) (format "\\href{%s}{%s}" path desc)) > ((eq format 'ascii) (format "%s (%s)" desc path)) > (t path))) > > Perhaps this could be included in the standard Org distribution as a > fallback option for exporting non-standard link types. Emacs/Org does > nothing with the link. The user is responsible for ensuring the output > is correct. This is already the default behavior for custom types. You don't even need to use `org-raw-export' or `org-raw-open'. All is needed, is (org-add-link-type "raw") Org requires it so it can tell if the link is an internal link or not. However, I don't think we need to introduce a particular link type for that. Users can define whatever they want. Regards, -- Nicolas Goaziou From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Thum Subject: Re: non-standard link errors Date: Wed, 2 Mar 2016 10:11:11 +0100 Message-ID: <56D6AE2F.8000103@gmx.de> References: <87vb5bdtl2.fsf@nicolasgoaziou.fr> <874mctck6y.fsf@nicolasgoaziou.fr> <87wppnz8th.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58771) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ab2nW-0003RJ-LA for emacs-orgmode@gnu.org; Wed, 02 Mar 2016 04:10:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ab2nS-0003v3-Kr for emacs-orgmode@gnu.org; Wed, 02 Mar 2016 04:10:22 -0500 Received: from mout.gmx.net ([212.227.15.18]:53533) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ab2nS-0003ug-Al for emacs-orgmode@gnu.org; Wed, 02 Mar 2016 04:10:18 -0500 In-Reply-To: <87wppnz8th.fsf@nicolasgoaziou.fr> 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Skip Collins , emacs-org list , Nicolas Goaziou Hi, this reminds me of my issue with tel: links. I also would have preferred to have them exported "pass-through", but AFAICT this requires me to come up with a trival function for every possible backend: those I know, those I don't, and those that may not exist yet. I cannot switch to the raw: solution (due to vcard export). I'm not currently experiencing problems, but I would like to suggest that maybe such a trival default handler could be added to the backends as some well-known property to be available to those who set the broken link handler to e.g. 'fallback. The onus would be on the user to do this, since correctness of output may suffer. Of course, basic sanitation should still be done in such a handler, but preferably no spectacular failure*. Cheers, Simon (*) Because I sync using org exporter, I tend to suffer from those. And yes, I'd rather have wrong output I can diagnose than nothing. On 02/29/2016 07:10 PM, Nicolas Goaziou wrote: > Hello, > > Skip Collins writes: > >> I have come up with a better solution than globally passing "broken" >> links. I defined a new "raw" link type. So now if I want to put a >> non-standard link in my export, I can do something like: >> Here is a [[raw:foo:/\bar, baz][bad link]]. >> which is exported in html as: >> Here is a bad link. >> >> Now I can have non-standard links included in the output without >> disabling link checking for all standard link types. This is how it is >> defined in my .emacs: >> (org-add-link-type "raw" 'org-raw-follow 'org-raw-export) >> (defun org-raw-follow (path)) >> (defun org-raw-export (path desc format) >> "Export a raw link. >> See `org-add-link-type' for details about PATH, DESC and FORMAT." >> (cond >> ((eq format 'html) (format "%s" path desc)) >> ((eq format 'latex) (format "\\href{%s}{%s}" path desc)) >> ((eq format 'ascii) (format "%s (%s)" desc path)) >> (t path))) >> >> Perhaps this could be included in the standard Org distribution as a >> fallback option for exporting non-standard link types. Emacs/Org does >> nothing with the link. The user is responsible for ensuring the output >> is correct. > > This is already the default behavior for custom types. You don't even > need to use `org-raw-export' or `org-raw-open'. All is needed, is > > (org-add-link-type "raw") > > Org requires it so it can tell if the link is an internal link or not. > However, I don't think we need to introduce a particular link type for > that. Users can define whatever they want. > > > Regards, > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: non-standard link errors Date: Wed, 02 Mar 2016 10:28:22 +0100 Message-ID: <87twkpp6tl.fsf@nicolasgoaziou.fr> References: <87vb5bdtl2.fsf@nicolasgoaziou.fr> <874mctck6y.fsf@nicolasgoaziou.fr> <87wppnz8th.fsf@nicolasgoaziou.fr> <56D6AE2F.8000103@gmx.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35114) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ab331-0000tw-KN for emacs-orgmode@gnu.org; Wed, 02 Mar 2016 04:26:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ab32y-00081i-Co for emacs-orgmode@gnu.org; Wed, 02 Mar 2016 04:26:23 -0500 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:55639) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ab32y-000812-61 for emacs-orgmode@gnu.org; Wed, 02 Mar 2016 04:26:20 -0500 In-Reply-To: <56D6AE2F.8000103@gmx.de> (Simon Thum's message of "Wed, 2 Mar 2016 10:11:11 +0100") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Simon Thum Cc: Skip Collins , emacs-org list Hello, Simon Thum writes: > this reminds me of my issue with tel: links. I also would have > preferred to have them exported "pass-through", but AFAICT this > requires me to come up with a trival function for every possible > backend: those I know, those I don't, and those that may not exist > yet. > > I cannot switch to the raw: solution (due to vcard export). I'm not > currently experiencing problems, but I would like to suggest that > maybe such a trival default handler could be added to the backends as > some well-known property to be available to those who set the broken > link handler to e.g. 'fallback. The onus would be on the user to do > this, since correctness of output may suffer. Of course, basic > sanitation should still be done in such a handler, but preferably no > spectacular failure*. As I explained, there is already a default handler in every major back-end. However, Org needs to tell links with a type from the others (internal links). This is what `org-add-link-type' is for. This has nothing to do with export. To put it differently, when Org encounters a foo:bar link, there are two options. Either "foo" is a registered link type, or not. If the former, Org tries to use whatever export function was provided, or fall-backs to the default handler. In the latter, Org considers it to be an internal link. Since there is probably no #+NAME: foo:bar, <> or * foo:bar in the document, the export process returns an error, by default. Regards, -- Nicolas Goaziou From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Thum Subject: Re: non-standard link errors Date: Wed, 2 Mar 2016 11:46:35 +0100 Message-ID: <56D6C48B.9070509@gmx.de> References: <87vb5bdtl2.fsf@nicolasgoaziou.fr> <874mctck6y.fsf@nicolasgoaziou.fr> <87wppnz8th.fsf@nicolasgoaziou.fr> <56D6AE2F.8000103@gmx.de> <87twkpp6tl.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59086) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ab4Ho-00028S-MD for emacs-orgmode@gnu.org; Wed, 02 Mar 2016 05:45:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ab4Hk-0006Wj-Cz for emacs-orgmode@gnu.org; Wed, 02 Mar 2016 05:45:44 -0500 Received: from mout.gmx.net ([212.227.17.20]:57221) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ab4Hj-0006Wd-Sn for emacs-orgmode@gnu.org; Wed, 02 Mar 2016 05:45:40 -0500 In-Reply-To: <87twkpp6tl.fsf@nicolasgoaziou.fr> 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou , emacs-org list Hi, after some testing I see my assumption that without export function no links are generated was wrong. All fine, and thanks for your tirelessness in explaining it so even I get it ;) Cheers, Simon On 03/02/2016 10:28 AM, Nicolas Goaziou wrote: > Hello, > > Simon Thum writes: > >> this reminds me of my issue with tel: links. I also would have >> preferred to have them exported "pass-through", but AFAICT this >> requires me to come up with a trival function for every possible >> backend: those I know, those I don't, and those that may not exist >> yet. >> >> I cannot switch to the raw: solution (due to vcard export). I'm not >> currently experiencing problems, but I would like to suggest that >> maybe such a trival default handler could be added to the backends as >> some well-known property to be available to those who set the broken >> link handler to e.g. 'fallback. The onus would be on the user to do >> this, since correctness of output may suffer. Of course, basic >> sanitation should still be done in such a handler, but preferably no >> spectacular failure*. > > As I explained, there is already a default handler in every major > back-end. > > However, Org needs to tell links with a type from the others (internal > links). This is what `org-add-link-type' is for. This has nothing to do > with export. > > To put it differently, when Org encounters a foo:bar link, there are two > options. Either "foo" is a registered link type, or not. If the former, > Org tries to use whatever export function was provided, or fall-backs to > the default handler. In the latter, Org considers it to be an internal > link. Since there is probably no #+NAME: foo:bar, <> > or * foo:bar in the document, the export process returns an error, by > default. > > > Regards, >