all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Chris Randle" <chris@amlog.co.uk>
To: emacs-orgmode@gnu.org
Subject: Values of org-indirect-buffer-display
Date: Wed, 17 Oct 2007 11:38:36 +0100	[thread overview]
Message-ID: <001401c810a9$e5b8f380$6a80a8c0@CUBE> (raw)

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

             reply	other threads:[~2007-10-17 10:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 10:38 Chris Randle [this message]
2007-10-17 11:15 ` foldout.el (was Re: Values of org-indirect-buffer-display) Adam Spiers
2007-11-02 14:35 ` Values of org-indirect-buffer-display Carsten Dominik

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001401c810a9$e5b8f380$6a80a8c0@CUBE' \
    --to=chris@amlog.co.uk \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.