From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matt Lundin <mdl@imapmail.org>
Subject: Re: Following links in an indirect buffer
Date: Tue, 29 Mar 2011 20:42:16 -0400
Message-ID: <87wrjhsal3.fsf@fastmail.fm>
References: <4D8215DD.9030103@slugfest.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=50533 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Q4jUL-0001r4-TE
	for emacs-orgmode@gnu.org; Tue, 29 Mar 2011 20:42:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lundin@fastmail.fm>) id 1Q4jUJ-000776-Uq
	for emacs-orgmode@gnu.org; Tue, 29 Mar 2011 20:42:20 -0400
Received: from out3.smtp.messagingengine.com ([66.111.4.27]:34964)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lundin@fastmail.fm>) id 1Q4jUJ-00076y-NR
	for emacs-orgmode@gnu.org; Tue, 29 Mar 2011 20:42:19 -0400
In-Reply-To: <4D8215DD.9030103@slugfest.demon.co.uk> (Shaun Johnson's message
	of "Thu, 17 Mar 2011 14:08:29 +0000")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/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: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Shaun Johnson <shaun@slugfest.demon.co.uk>
Cc: Org Mode <emacs-orgmode@gnu.org>

Shaun Johnson <shaun@slugfest.demon.co.uk> writes:

> Hi all,
>
> I regularly work in an indirect buffer created by org-tree-to-indirect-buffer.
>
> Following an id: type link in such a buffer seems to always switche to the
> base buffer even if the target is visible in the indirect buffer.

If you have org-id-track-globally set to t, org-mode will query a hash
table to determine in which file the id is located. The result will
always be the base file. (Contrast this with [[target]] links, which
prompt a simple search in the current buffer.)

> Is the buffer switching intended behaviour or is this a bug?

I wouldn't call it a bug. But I think an option to search first in the
current buffer might be a feature request. :)

>
> Following an ordinary link (like [[Target]]) does not exhibit this buffer
> switching behaviour. However if the target is outside the visible part of
> the indirect buffer the buffer will be widened and point will move to the
> target but only after being told that there is no match and asked if I want
> to create a new heading.

This seems a bug to me, since the buffer is widened and the correct
target found after the warning.

Best,
Matt