all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Christopher Howard <christopher@librehacker.com>
Cc: Help Gnu Emacs Mailing List <help-gnu-emacs@gnu.org>
Subject: Re: help et. al - use different frame instead of splitting frame?
Date: Wed, 15 May 2024 12:35:10 +0700	[thread overview]
Message-ID: <CAP_d_8U5Z22cCbiqFac0KpH0s+2ZVMnE=wn5x4OSpFVUtTX0MQ@mail.gmail.com> (raw)
In-Reply-To: <87ttj0rzv1.fsf@librehacker.com>

On Wed, 15 May 2024 at 08:57, Christopher Howard
<christopher@librehacker.com> wrote:

> Hi, use Emacs with multiple frames, one on each monitor, and typically one window per frame. Now that I have lots of frame space, I find it annoying when functions like (describe-function) split the frame I am on. I am wondering if it is possible to change something so that functions like that instead display the buffer in a different frame.
>
> Looking for someplace to start, I dove down into `describe-function' source code and eventually found myself trying to hack temp-buffer-window-show

You either went too deep or not deep enough ;)

The place you want is called display-buffer-alist and it’s a variable
containing rules for activating various windows. See the manual and
one of several tutorials on it, like this one:

https://www.masteringemacs.org/article/demystifying-emacs-window-manager



      parent reply	other threads:[~2024-05-15  5:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 18:51 help et. al - use different frame instead of splitting frame? Christopher Howard
2024-05-15  2:38 ` [External] : " Drew Adams
2024-06-24  6:19   ` Björn Bidar
     [not found]   ` <87v81ylv5f.fsf@>
2024-06-24 14:31     ` Drew Adams
2024-05-15  5:35 ` Yuri Khan [this message]

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='CAP_d_8U5Z22cCbiqFac0KpH0s+2ZVMnE=wn5x4OSpFVUtTX0MQ@mail.gmail.com' \
    --to=yuri.v.khan@gmail.com \
    --cc=christopher@librehacker.com \
    --cc=help-gnu-emacs@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.