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
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
> y
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 r
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 h
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
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
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 iPho
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 particula
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 so
