From: "Eddward DeVilla" <eddward@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: link bug w/ indirect buffers
Date: Tue, 10 Jul 2007 09:46:10 -0500 [thread overview]
Message-ID: <b71b18520707100746n4f729959wc172a7d6530d91b2@mail.gmail.com> (raw)
In-Reply-To: <04a641adbeca8cb12fd6c066c6c8aec7@science.uva.nl>
Sounds good. Thanks!
On 7/10/07, Carsten Dominik <dominik@science.uva.nl> wrote:
> Unfortunately I have also not found a better solution. So
> it now should use the base buffer, and widen it if necessary.
>
> - Carsten
>
> On Mar 28, 2007, at 0:34, Eddward DeVilla wrote:
>
> > Hi,
> >
> > I found a bug involving indirect buffers when following links. If
> > I have one file with a link to a second file and I have that second
> > file opened with an indirect buffer narrowed such that the link is not
> > contained in the narrowed region, org may fail to follow the link.
> > Basically, if a file is opened in several indirect buffers, org
> > only looks in the buffer (indirect or otherwise) most recently
> > touched. I have seen org do this before with buffer cycling and that
> > has been fixed. I'm guessing this is a related issue, but I have
> > tracked it down yet.
> > I guess the easiest 'right' behavior would be to have the link
> > open the base buffer for the file. I have to admit though, when doing
> > a heading search where the heading is already in its own indirect
> > buffer, I like it when it finds that buffer. I can't think of a good
> > set of rules to define that behavior.
> >
> > Edd
> >
> >
> > _______________________________________________
> > Emacs-orgmode mailing list
> > Emacs-orgmode@gnu.org
> > http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> >
> >
>
> --
> Carsten Dominik
> Sterrenkundig Instituut "Anton Pannekoek"
> Universiteit van Amsterdam
> Kruislaan 403
> NL-1098SJ Amsterdam
> phone: +31 20 525 7477
>
>
prev parent reply other threads:[~2007-07-10 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 22:34 link bug w/ indirect buffers Eddward DeVilla
2007-07-10 5:54 ` Carsten Dominik
2007-07-10 14:46 ` Eddward DeVilla [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=b71b18520707100746n4f729959wc172a7d6530d91b2@mail.gmail.com \
--to=eddward@gmail.com \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
/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).