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.