Unable to resolve link: nil

Unable to resolve link: nil

[Vikas Rawal]

Working on long, complex documents, I sometimes have a wrongly pointed link. And when I try to export it, I get the error: "Unable to resolve link: nil”. Is there a straightforward way to find out which link is not resolving?

Vikas

Re: Unable to resolve link: nil

[Michael Welle]

Hello,

Vikas Rawal <vikaslists@agrarianresearch.org> writes:

> Working on long, complex documents, I sometimes have a wrongly pointed
> link. And when I try to export it, I get the error: "Unable to resolve
> link: nil”. Is there a straightforward way to find out which link is
> not resolving?
good question ;). I spent half an hour this week in a similar situation ;).
I used bisecting to find the problem. In my case it was a space before
the protocol: [[ http://foo.bar][foo]].

Regards
hmw

Re: Unable to resolve link: nil

[Nick Dokos]

Michael Welle <mwe012008@gmx.net> writes:

> Hello,
>
> Vikas Rawal <vikaslists@agrarianresearch.org> writes:
>
>> Working on long, complex documents, I sometimes have a wrongly pointed
>> link. And when I try to export it, I get the error: "Unable to resolve
>> link: nil”. Is there a straightforward way to find out which link is
>> not resolving?
> good question ;). I spent half an hour this week in a similar situation ;).
> I used bisecting to find the problem. In my case it was a space before
> the protocol: [[ http://foo.bar][foo]].
>

(untested)

Does org-lint help? 

-- 
Nick

Re: Unable to resolve link: nil

[Michael Welle]

Hello,

Nick Dokos <ndokos@gmail.com> writes:

> Michael Welle <mwe012008@gmx.net> writes:
>
>> Hello,
>>
>> Vikas Rawal <vikaslists@agrarianresearch.org> writes:
>>
>>> Working on long, complex documents, I sometimes have a wrongly pointed
>>> link. And when I try to export it, I get the error: "Unable to resolve
>>> link: nil”. Is there a straightforward way to find out which link is
>>> not resolving?
>> good question ;). I spent half an hour this week in a similar situation ;).
>> I used bisecting to find the problem. In my case it was a space before
>> the protocol: [[ http://foo.bar][foo]].
>>
>
> (untested)
>
> Does org-lint help? 
ah, learned something new here ;). Yes, it catches the space.

Regards
hmw

Re: Unable to resolve link: nil

[Vikas Rawal]

> 
> (untested)
> 
> Does org-lint help? 

Oh wow!

Thanks.

Vikas

Re: Unable to resolve link: nil

[Vikas Rawal]

> 
>> 
>> (untested)
>> 
>> Does org-lint help? 
> 
> Oh wow!
> 

org-lint helped identify several errors but this problem remains.

Vikas

Re: Unable to resolve link: nil

[Michael Welle]

Hello,

Vikas Rawal <vikaslists@agrarianresearch.org> writes:

>> 
>>> 
>>> (untested)
>>> 
>>> Does org-lint help? 
>> 
>> Oh wow!
>> 
>
> org-lint helped identify several errors but this problem remains.
hm, maybe grep for [[ or [ and peer at the result. Other than that I have no
idea.

Regards
hmw

Re: Unable to resolve link: nil

[Vikas Rawal]

> 
>> Working on long, complex documents, I sometimes have a wrongly pointed
>> link. And when I try to export it, I get the error: "Unable to resolve
>> link: nil”. Is there a straightforward way to find out which link is
>> not resolving?
> good question ;). I spent half an hour this week in a similar situation ;).
> I used bisecting to find the problem. In my case it was a space before
> the protocol: [[ http://foo.bar][foo]].


I am unable to export individual headlines because of many cross-references. An individual headline refuses to export because of them. So, exporting parts of the document to narrow down to the part where the problem is does not work for me.

Vikas 

Re: Unable to resolve link: nil

[Nicolas Goaziou]

Hello,

Vikas Rawal <vikaslists@agrarianresearch.org> writes:

> I am unable to export individual headlines because of many
> cross-references. An individual headline refuses to export because of
> them. So, exporting parts of the document to narrow down to the part
> where the problem is does not work for me.

See `org-export-with-broken-links'.

Regards,

-- 
Nicolas Goaziou