From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Welle <mwe012008@gmx.net>
Subject: Re: Unable to resolve link: nil
Date: Fri, 22 Jul 2016 21:34:53 +0200
Message-ID: <t39a6dxeqn.ln2@news.c0t0d0s0.de>
References: <6390D7C2-81B9-4CC8-8FD9-B852966643C1@agrarianresearch.org>
	<7o3a6dxj3m.ln2@news.c0t0d0s0.de>
	<87y44txyzw.fsf@alphaville.usersys.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60945)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1bQgE7-00022p-PL
	for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 15:35:16 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1bQgE3-00055T-LM
	for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 15:35:14 -0400
Received: from plane.gmane.org ([80.91.229.3]:33915)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1bQgE3-00055M-Dz
	for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 15:35:11 -0400
Received: from list by plane.gmane.org with local (Exim 4.69)
	(envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1bQgE0-00039t-T2
	for emacs-orgmode@gnu.org; Fri, 22 Jul 2016 21:35:08 +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 <emacs-orgmode@gnu.org>; Fri, 22 Jul 2016 21:35:08 +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 <emacs-orgmode@gnu.org>; Fri, 22 Jul 2016 21:35:08 +0200
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: emacs-orgmode@gnu.org

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