unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: Christopher Howard <christopher@librehacker.com>,
	 Help Gnu Emacs Mailing List <help-gnu-emacs@gnu.org>
Subject: Re: [External] : help et. al - use different frame instead of splitting frame?
Date: Mon, 24 Jun 2024 09:19:56 +0300	[thread overview]
Message-ID: <18249.6166018367$1719210070@news.gmane.org> (raw)
In-Reply-To: <SJ0PR10MB54888C020915CF92374EF42CF3EC2@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Wed, 15 May 2024 02:38:29 +0000")

Drew Adams <drew.adams@oracle.com> writes:

>> 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.
>
> Just customize `special-display-buffer-names'
> or `special-display-regexps'.
>
> E.g., I use `special-display-buffer-names'
> to put *Help* and *Completions* buffers in
> their own frames that look different.  I put
> other *...* buffers in frames with a third
> look by setting `special-display-regexps' to
> ("[ ]?[*][^*]+[*]").
>
> A "special-display" buffer is shown in its own
> dedicated frame (you can get more refined than
> that, if you like).
>
> Emacs will tell you that these options are
> obsolete.  But they're simple to use and they
> still work perfectly fine.
>
> If you instead want to complicate your life,
> you can do what those options do and much,
> more by customizing `display-buffer-alist'
> or its ilk.  See the Elisp manual, node
> `Displaying Buffers' and all of its progeny.
>
> https://www.gnu.org/software/emacs/manual/html_node/elisp/Displaying-Buffers.html

Another option is to use pop-up-frames instead if you want to go fully
frames instead of windows.

Pop-up-frames will make every new window open a new frame instead.



  reply	other threads:[~2024-06-24  6:19 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 [this message]
     [not found]   ` <87v81ylv5f.fsf@>
2024-06-24 14:31     ` Drew Adams
2024-05-15  5:35 ` Yuri Khan

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to='18249.6166018367$1719210070@news.gmane.org' \
    --to=bjorn.bidar@thaodan.de \
    --cc=christopher@librehacker.com \
    --cc=drew.adams@oracle.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).