From: Noam Postavsky <npostavs@users.sourceforge.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 25511@debbugs.gnu.org, Katsumi Yamaoka <yamaoka@jpl.org>
Subject: bug#25511: 26.0.50; modify-frame-parameters modifies undesignated parameter?
Date: Mon, 23 Jan 2017 12:27:23 -0500 [thread overview]
Message-ID: <CAM-tV-93EhBgkUakRHXWD3hjxo3jiaxfE4ZB5W703SmGy28VKg@mail.gmail.com> (raw)
In-Reply-To: <5885B8D7.4040301@gmx.at>
On Mon, Jan 23, 2017 at 3:03 AM, martin rudalics <rudalics@gmx.at> wrote:
>
>> On the new frame, (frame-parameter nil 'left) returns 8, that is
>> outside of the down screen. This happens whichever the original
>> frame (that runs the script) exists in the up screen or the down
>> screen. As mentioned above, a new frame did not protrude from
>> the down screen last week. Here is a workaround:
>>
>> (let ((frame (make-frame)))
>> (sit-for 0)
>> (modify-frame-parameters frame '((top . 1200))))
>>
>> But it is needless, isn't it?
>
> IIUC your approach worked because of a busy loop in x_make_frame_visible
> which has been removed a few days ago. I back its removal so you should
> be able to do without it.
Should we change modify-frame-parameters to delay the actual
modification until the frame turns visible?
next prev parent reply other threads:[~2017-01-23 17:27 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM-tV-93EhBgkUakRHXWD3hjxo3jiaxfE4ZB5W703SmGy28VKg@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=25511@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--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 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.