Subject: bug#15684: 24.3.50; `set-frame-parameter' broken for parameter `minibuffer'

From: martin rudalics <[email-masked]>
Date: Sat, 04 Jan 2014 15:12:53 +0100

> emacs -Q
 >
 > C-x 5 2
 >
 > M-: (pp-eval-expression '(frame-parameters))
 >
 > Value of parameter `minibuffer' is a window.
 >
 > M-: (set-frame-parameter nil 'minibuffer t)
 >
 > M-: (pp-eval-expression '(frame-parameters))
 >
 > Value of parameter `minibuffer' is unchanged: still the window.
 > Should be t.
 >
 > M-: (set-frame-parameter nil 'minibuffer nil)
 >
 > Value of parameter `minibuffer' is unchanged: still the window.
 > Should be nil.
 >
 > M-x set-variable default-frame-alist
 >
 > ((tool-bar-lines . 0)
 >  (menu-bar-lines . 1)
 >  (minibuffer))
 >
 > C-x 5 2
 >
 > The new frame is created without a minibuffer, as it should be.  Check
 > it with `M-: (pp-eval-expression '(frame-parameters))', with that frame
 > selected.
 >
 > M-: (set-frame-parameter nil 'minibuffer t)
 >
 > M-: (pp-eval-expression '(frame-parameters))
 >
 > Value of parameter `minibuffer' is unchanged: still nil.  Should be t.
 >
 > See Subject line.

Please read the Elisp manual before submitting such reports:

These frame parameters, meaningful on all kinds of terminals, deal with
which buffers have been, or should, be displayed in the frame.

`minibuffer'
      Whether this frame has its own minibuffer.  The value `t' means
      yes, `nil' means no, `only' means this frame is just a minibuffer.
      If the value is a minibuffer window (in some other frame), the
      frame uses that minibuffer.

      This frame parameter takes effect when the frame is created, and
      can not be changed afterwards.

Thanks, martin