From: Matt Lundin <mdl@imapmail.org>
To: Shaun Johnson <shaun@slugfest.demon.co.uk>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Following links in an indirect buffer
Date: Tue, 29 Mar 2011 20:42:16 -0400 [thread overview]
Message-ID: <87wrjhsal3.fsf@fastmail.fm> (raw)
In-Reply-To: <4D8215DD.9030103@slugfest.demon.co.uk> (Shaun Johnson's message of "Thu, 17 Mar 2011 14:08:29 +0000")
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
prev parent reply other threads:[~2011-03-30 0:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 14:08 Following links in an indirect buffer Shaun Johnson
2011-03-30 0:42 ` Matt Lundin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wrjhsal3.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=emacs-orgmode@gnu.org \
--cc=shaun@slugfest.demon.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).