From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eddward DeVilla" Subject: link bug w/ indirect buffers Date: Tue, 27 Mar 2007 17:34:57 -0500 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HWKIE-0002p3-53 for emacs-orgmode@gnu.org; Tue, 27 Mar 2007 18:37:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HWKIC-0002nD-Jl for emacs-orgmode@gnu.org; Tue, 27 Mar 2007 18:37:29 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HWKIC-0002my-GM for emacs-orgmode@gnu.org; Tue, 27 Mar 2007 17:37:28 -0500 Received: from wr-out-0506.google.com ([64.233.184.232]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HWKFn-0003Lk-86 for emacs-orgmode@gnu.org; Tue, 27 Mar 2007 18:34:59 -0400 Received: by wr-out-0506.google.com with SMTP id i23so2175374wra for ; Tue, 27 Mar 2007 15:34:58 -0700 (PDT) Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: emacs-orgmode 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