From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Unable to resolve link: nil Date: Fri, 22 Jul 2016 15:18:43 -0400 Message-ID: <87y44txyzw.fsf@alphaville.usersys.redhat.com> References: <6390D7C2-81B9-4CC8-8FD9-B852966643C1@agrarianresearch.org> <7o3a6dxj3m.ln2@news.c0t0d0s0.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58465) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQfyP-0005yO-06 for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 15:19:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bQfyL-00022E-BI for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 15:19:00 -0400 Received: from plane.gmane.org ([80.91.229.3]:33067) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQfyL-00021m-44 for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 15:18:57 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1bQfyJ-0006x5-AC for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 21:18:55 +0200 Received: from nat-pool-bos-t.redhat.com ([66.187.233.206]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 22 Jul 2016 21:18:55 +0200 Received: from ndokos by nat-pool-bos-t.redhat.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 22 Jul 2016 21:18:55 +0200 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" To: emacs-orgmode@gnu.org 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? > 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