From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Welle Subject: Re: Unable to resolve link: nil Date: Fri, 22 Jul 2016 20:03:19 +0200 Message-ID: <7o3a6dxj3m.ln2@news.c0t0d0s0.de> References: <6390D7C2-81B9-4CC8-8FD9-B852966643C1@agrarianresearch.org> 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]:45416) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQep5-0008Nd-1d for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 14:05:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bQep0-0004QG-0c for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 14:05:18 -0400 Received: from plane.gmane.org ([80.91.229.3]:57671) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQeoz-0004Q6-Pf for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 14:05:13 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1bQeow-0005CB-Qe for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 20:05:10 +0200 Received: from dslb-088-066-015-139.088.066.pools.vodafone-ip.de ([88.66.15.139]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 22 Jul 2016 20:05:10 +0200 Received: from mwe012008 by dslb-088-066-015-139.088.066.pools.vodafone-ip.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 22 Jul 2016 20:05:10 +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 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]]. Regards hmw