From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spiers Subject: foldout.el (was Re: Values of org-indirect-buffer-display) Date: Wed, 17 Oct 2007 12:15:17 +0100 Message-ID: <20071017111517.GA10874@atlantic.linksys.moosehall> References: <001401c810a9$e5b8f380$6a80a8c0@CUBE> Reply-To: Adam Spiers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ii6s2-00068R-T9 for emacs-orgmode@gnu.org; Wed, 17 Oct 2007 07:15:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ii6rw-00067s-Pf for emacs-orgmode@gnu.org; Wed, 17 Oct 2007 07:15:25 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ii6rw-00067p-Mc for emacs-orgmode@gnu.org; Wed, 17 Oct 2007 07:15:20 -0400 Received: from mail.beimborn.com ([70.84.38.100]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ii6rw-0007YX-Bu for emacs-orgmode@gnu.org; Wed, 17 Oct 2007 07:15:20 -0400 Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1]) by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id l9HBFJIJ017979 for ; Wed, 17 Oct 2007 06:15:19 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id l9HBFJai017974 for emacs-orgmode@gnu.org; Wed, 17 Oct 2007 12:15:19 +0100 Content-Disposition: inline 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: emacs-orgmode@gnu.org On Wed, Oct 17, 2007 at 11:38:36AM +0100, 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. This is probably not useful to you, but I just wanted to mention in case it is useful to others, that foldout.el works quite nicely in combination with org-mode, for narrowing to subtrees. It works recursively too. (autoload 'foldout-exit-fold "foldout") (autoload 'foldout-zoom-subtree "foldout") (mapc (lambda (mode) (add-hook mode (lambda () ;; Quick navigation (local-set-key [(shift left)] 'foldout-exit-fold) (local-set-key [(shift right)] 'foldout-zoom-subtree) ))) '(outline-mode-hook outline-minor-mode-hook))