From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Chris Randle" Subject: Values of org-indirect-buffer-display Date: Wed, 17 Oct 2007 11:38:36 +0100 Message-ID: <001401c810a9$e5b8f380$6a80a8c0@CUBE> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ii6Iq-0002hY-CM for emacs-orgmode@gnu.org; Wed, 17 Oct 2007 06:39:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ii6Io-0002gm-AB for emacs-orgmode@gnu.org; Wed, 17 Oct 2007 06:39:03 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ii6Io-0002gW-5F for emacs-orgmode@gnu.org; Wed, 17 Oct 2007 06:39:02 -0400 Received: from anchor-post-30.mail.demon.net ([194.217.242.88]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ii6Im-0000Ia-P9 for emacs-orgmode@gnu.org; Wed, 17 Oct 2007 06:39:01 -0400 Received: from amlog.demon.co.uk ([80.177.106.135] helo=CUBE) by anchor-post-30.mail.demon.net with esmtp (Exim 4.67) id 1Ii6Ii-00003L-1s for emacs-orgmode@gnu.org; Wed, 17 Oct 2007 10:38:57 +0000 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@gnu.org 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. -- Chris Randle