all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: 25946@debbugs.gnu.org
Subject: bug#25946: 26.0.50; display-buffer ignores ignores reusable-frames in display-buffer-alist
Date: Fri, 03 Mar 2017 11:01:43 +0100	[thread overview]
Message-ID: <877f46d6go.fsf@wi.uni-muenster.de> (raw)

Hi there,

I fail to get display-buffer-alist working.

Recipe starting from 'emacs -Q':
Eval this expression:
(customize-set-variable
 'display-buffer-alist
 '(("\\*shell\\*"
    . (display-buffer-pop-up-frame . '((reusable-frames . t))))))
M-x shell
A shell frame opens as expected.
M-x shell
A new frame is opened, while I expected the existing one to be
reused.

Actually, I'm sure that I do not understand the documentation for
display-buffer (redirected from display-buffer-alist).  Maybe that
is a separate bug.

In previous versions of Emacs, I used special-display-buffer-names,
which is obsolete now and points to the variable used above,
display-buffer-alist.  It would be great if the documentation for
that variable explained what to do.  In particular, I would like the
frame to be special/dedicated such that it disappears if the buffer
is killed.  Is that lack of documentation a separate bug?

Best wishes
Jens


In GNU Emacs 26.0.50 (build 1, x86_64-unknown-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2017-02-24 built on debian-8
Repository revision: 91932fff1ded8ed3b4d39dd06891f26960153b9e





             reply	other threads:[~2017-03-03 10:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 10:01 Jens Lechtenboerger [this message]
2017-03-03 10:38 ` bug#25946: 26.0.50; display-buffer ignores ignores reusable-frames in display-buffer-alist martin rudalics
2017-03-03 10:58   ` Jens Lechtenboerger
2017-03-03 14:24     ` martin rudalics
2017-03-03 14:49       ` Jens Lechtenboerger
2017-03-03 18:23         ` martin rudalics
2017-03-03 18:55           ` Drew Adams
     [not found]           ` <13CD49F822DC4A42AF94C24270D9E5CF9A5D4E36@WIWI-MAIL-1.WIWI.UNI-MUENSTER.DE>
2017-03-04 17:08             ` Jens Lechtenboerger
2017-03-04 17:40           ` martin rudalics
2017-03-05 10:34             ` martin rudalics
2017-03-05 11:27               ` Stephen Berman
2017-03-05 13:28                 ` martin rudalics
2017-03-05 22:20                   ` Michael Heerdegen
2017-03-06  8:11                     ` martin rudalics
2017-03-06  8:57                     ` Stephen Berman
2017-03-06  9:25                       ` Jens Lechtenboerger
2017-03-06 11:07                         ` Stephen Berman
2017-03-06 17:46                           ` martin rudalics
2017-03-06 20:59                             ` Stephen Berman
2017-03-07  9:45                               ` martin rudalics
2017-03-07 16:51                                 ` Stephen Berman
2017-03-07 19:00                                   ` martin rudalics
2017-03-07 19:36                                     ` Stephen Berman
2017-03-10 15:01                                   ` Jens Lechtenboerger
2017-03-11 10:20                                     ` martin rudalics
2017-03-06 17:46                         ` martin rudalics

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=877f46d6go.fsf@wi.uni-muenster.de \
    --to=lechten@wi.uni-muenster.de \
    --cc=25946@debbugs.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.