all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
Cc: 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 15:24:47 +0100	[thread overview]
Message-ID: <58B97CAF.6060600@gmx.at> (raw)
In-Reply-To: <87zih2bp98.fsf@wi.uni-muenster.de>

 > Indeed.  Nevertheless that function seemed to be the closest
 > candidate coming from the documentation on obsolete functionality
 > for special frames.

Please suggest better documentation then.

 >> Please read also this
 >>
 >>       If ALIST contains a `pop-up-frame-parameters' entry, the associated
 >>       value is added to the newly created frame's parameters.
 >
 > I did.  At what are you hinting?  I believe that for users this text
 > is not of much help as the Emacs manual contains next to nothing on
 > frame parameters but points to the elisp manual.

The text is from the Elisp manual and I hinted at it because I thought
there was a frame parameter for controlling dedicatedness.  I was wrong
- there is no such parameter.  You rather have to set the variable
‘display-buffer-mark-dedicated’ to non-nil or bind it around the
‘display-buffer’ call.  That's very ugly.  I think we should provide an
alist entry like the `reusable-frames' one to control the dedicateness
of the window used.

martin






  reply	other threads:[~2017-03-03 14:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 10:01 bug#25946: 26.0.50; display-buffer ignores ignores reusable-frames in display-buffer-alist Jens Lechtenboerger
2017-03-03 10:38 ` martin rudalics
2017-03-03 10:58   ` Jens Lechtenboerger
2017-03-03 14:24     ` martin rudalics [this message]
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=58B97CAF.6060600@gmx.at \
    --to=rudalics@gmx.at \
    --cc=25946@debbugs.gnu.org \
    --cc=lechten@wi.uni-muenster.de \
    /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.