From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Values of org-indirect-buffer-display Date: Fri, 2 Nov 2007 15:35:51 +0100 Message-ID: <7048B7F5-9F37-4364-835C-7669D7C634D0@science.uva.nl> References: <001401c810a9$e5b8f380$6a80a8c0@CUBE> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Io5ga-00028g-5d for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 19:12:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Io5gY-000265-Ik for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 19:12:19 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Io5gY-00025n-89 for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 19:12:18 -0400 Received: from fk-out-0910.google.com ([209.85.128.184]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Io5gX-0004ym-Qi for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 19:12:18 -0400 Received: by fk-out-0910.google.com with SMTP id 19so1320654fkr for ; Fri, 02 Nov 2007 16:12:17 -0700 (PDT) In-Reply-To: <001401c810a9$e5b8f380$6a80a8c0@CUBE> 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: Chris Randle Cc: emacs-orgmode@gnu.org On 17Oct2007, at 12:38 PM, Chris Randle wrote: > I'm new to emacs and org-mode, so please forgive me if I've missed > something fundamental. > > I've been using org-tree-to-indirect-buffer bound to the default C- > c C-x > b, and saw in the help that you can modify org-indirect-buffer- > display. > In my .emacs file, I've got the following: > > (setq org-indirect-buffer-display 'new-frame) > > When I hit C-c C-x b on a subtree, I do indeed get a narrowed > subtree in > a new frame (call it frame 2). When I go back to the original frame > and > repeat for a different subtree, that works too, but the buffer in > frame > 2 is killed. The help for org-tree-to-indirect-buffer says that a C-u > prefix will keep the last buffer, and this works as stated: the buffer > in frame 2 is then kept. > > So my question: if C-u controls the persistence of the previous > buffer, > what is intended difference between new-frame and dedicated-frame? > > I had expected C-c C-x b with new-frame to work the same as C-u C-c > C-x > b with dedicated-frame, and I feel that new-frame is redundant. I > don't > see why anyone would want to keep opening new frames whilst killing > the > indirect buffers in the previous ones. Yes, you are right here. I plan the following change, please comment: When `org-indirect-buffer-display' is `new-frame', the old buffer is always kept and C-u would be redundant. For any other value of `org-indirect- buffer-display', the C-u prefix will keep the old buffer. I guess this still means that `new-frame' is the least useful value of this variable, but still it might find its applications. - Carsten