From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 13937@debbugs.gnu.org
Subject: bug#13937: 24.3.50; `make-frame' broken for `fullscreen' parameter on MS Windows
Date: Wed, 13 Mar 2013 19:34:15 +0200 [thread overview]
Message-ID: <834ngfjjag.fsf@gnu.org> (raw)
In-Reply-To: <0940CF985FBB4FBAB83BC9356CC067F0@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Tue, 12 Mar 2013 15:21:31 -0700
>
> emacs -Q
>
> In *scratch*, type this:
>
> (defun foo ()
> (interactive)
> (select-frame (make-frame '((minibuffer . t)
> (fullscreen . maximized)))))
>
> (frame-parameters)
>
> Evaluate the `foo' definition, then M-x foo.
>
> A new frame is created with the same content (good).
> However:
>
> 1. There is no minibuffer shown.
> 2. The frame is not maximized.
Fixed in trunk revision 112038. Thanks.
> Nevertheless, go to eob (put point after `(frame-parameters)'), and
> enter this (there will be no echo, so type carefully):
>
> M-x pp-eval-last-sexp RET
>
> You will see the frame parameters for the created frame. Among them you
> will see this parameter entry, which is correct (though the frame is NOT
> maximized): (fullscreen . maximized).
>
> And you will see this entry (or similar):
> (minibuffer . #<window 03B1A3F8 on *Minibuf-0*>)
>
> That is not correct wrt the arg to `make-frame'.
This part I don't get: why do you think this is incorrect?
> It seems that multiple things are broken, here.
Only one thing was broken, actually: the new frame dimensions were
stored, but the frame was not being resized.
next prev parent reply other threads:[~2013-03-13 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 22:21 bug#13937: 24.3.50; `make-frame' broken for `fullscreen' parameter on MS Windows Drew Adams
2013-03-13 17:34 ` Eli Zaretskii [this message]
2013-03-13 18:11 ` Drew Adams
2013-03-13 18:25 ` Eli Zaretskii
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=834ngfjjag.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13937@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.