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