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, >