From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
Cc: 15684@debbugs.gnu.org
Subject: bug#15684: 24.3.50; `set-frame-parameter' broken for parameter `minibuffer'
Date: Sat, 04 Jan 2014 15:12:53 +0100 [thread overview]
Message-ID: <52C816E5.90300@gmx.at> (raw)
In-Reply-To: <68865b40-8f94-408c-bee8-c3a22ff8d0bb@default>
> 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
next prev parent reply other threads:[~2014-01-04 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 17:24 bug#15684: 24.3.50; `set-frame-parameter' broken for parameter `minibuffer' Drew Adams
2014-01-04 14:12 ` martin rudalics [this message]
2014-01-04 16:31 ` Drew Adams
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=52C816E5.90300@gmx.at \
--to=rudalics@gmx.at \
--cc=15684@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.