From: martin rudalics <rudalics@gmx.at>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 25511@debbugs.gnu.org
Subject: bug#25511: 26.0.50; modify-frame-parameters modifies undesignated parameter?
Date: Mon, 23 Jan 2017 11:28:14 +0100 [thread overview]
Message-ID: <5885DABE.9000408@gmx.at> (raw)
In-Reply-To: <b4mmveiywtp.fsf@jpl.org>
>> As a general rule: Never set a frame parameter right after creating a
>> new frame.
>
> Ok, I can modify some codes similar to it.
Try to avoid ‘modify-frame-parameters’ wherever it's possible. There
might be still cases left where we have to use it because some frame
parameters cannot be processed on an invisible frame. That's enough
trouble.
> In order not to hide the matte that includes the title bar, the
> menu bar, and the tool bar. In reality on Cygwin, the form
>
> (make-frame '((left . 0) (top . 0)))
>
> doesn't work as expected; the new frame appears on the down
> screen and the position is erratic.
Can you try this with a native Windows build and compare the behaviors?
> The minimum values that
> display a new frame fully on the top-left corner of the upper
> screen is:
>
> (make-frame '((left . 0) (top . 1)))
>
> But frame-parameters shows left=8 and top=32 in that case.
What does a specification like
(make-frame '((left . (+ -8)) (top . (+ -32))))
give here?
martin
next prev parent reply other threads:[~2017-01-23 10:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 7:28 bug#25511: 26.0.50; modify-frame-parameters modifies undesignated parameter? Katsumi Yamaoka
2017-01-23 8:03 ` martin rudalics
2017-01-23 9:01 ` Katsumi Yamaoka
2017-01-23 10:28 ` martin rudalics [this message]
2017-01-23 22:54 ` Katsumi Yamaoka
2017-01-24 0:45 ` Katsumi Yamaoka
2017-01-24 7:46 ` martin rudalics
2017-01-24 9:18 ` Katsumi Yamaoka
2017-01-24 9:37 ` martin rudalics
2017-06-05 12:57 ` npostavs
2017-06-05 13:36 ` martin rudalics
2017-06-06 0:00 ` npostavs
2017-06-06 6:38 ` martin rudalics
2017-01-24 7:46 ` martin rudalics
2017-01-23 17:27 ` Noam Postavsky
2017-01-23 18:01 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5885DABE.9000408@gmx.at \
--to=rudalics@gmx.at \
--cc=25511@debbugs.gnu.org \
--cc=yamaoka@jpl.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).