Re: [O] Unable to resolve link: nil

2016-07-23 Thread Nicolas Goaziou
Hello, Vikas Rawal 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-wit

Re: [O] Unable to resolve link: nil

2016-07-22 Thread 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 si

Re: [O] Unable to resolve link: nil

2016-07-22 Thread Vikas Rawal
> >> >> (untested) >> >> Does org-lint help? > > Oh wow! > org-lint helped identify several errors but this problem remains. Vikas

Re: [O] Unable to resolve link: nil

2016-07-22 Thread Vikas Rawal
> > (untested) > > Does org-lint help? Oh wow! Thanks. Vikas

Re: [O] Unable to resolve link: nil

2016-07-22 Thread Nick Dokos
Michael Welle writes: > Hello, > > Vikas Rawal 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? >

[O] Unable to resolve link: nil

2016-07-22 Thread 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: [O] unable to resolve link: nil?

2016-04-17 Thread Eric S Fraga
On Saturday, 16 Apr 2016 at 18:53, Nicolas Goaziou wrote: > You could also try using `org-lint' or setting #+OPTIONS: > broken-links:mark somewhere in your document. Thanks. I'll try to remember this for next time! -- : Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-705-g716e33

Re: [O] unable to resolve link: nil?

2016-04-16 Thread Nicolas Goaziou
Hello, Eric S Fraga writes: > In hindsight, the error makes sense: the problem was a missing colon (:) > in one of the links (lots of C-c C-x C-n to find it). Maybe it would > help to say a bit more, such as "no link type found" and maybe show the > rest of the contents of the link? Or even a

Re: [O] unable to resolve link: nil?

2016-04-16 Thread Eric S Fraga
On Saturday, 16 Apr 2016 at 17:35, Fraga, Eric wrote: > Hello, > > I have the error message: > > : user-error: unable to resolve link: nil > > on export to LaTeX. > > This is driving me crazy. I'm sure it's my fault but is there any way > to get some useful hint as to where I may be going wrong wi

[O] unable to resolve link: nil?

2016-04-16 Thread Eric S Fraga
Hello, I have the error message: : user-error: unable to resolve link: nil on export to LaTeX. This is driving me crazy. I'm sure it's my fault but is there any way to get some useful hint as to where I may be going wrong without having to bisect my rather large document? Thanks, eric -- :