From: Katsumi Yamaoka <yamaoka@jpl.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 25511@debbugs.gnu.org
Subject: bug#25511: 26.0.50; modify-frame-parameters modifies undesignated parameter?
Date: Tue, 24 Jan 2017 07:54:29 +0900 [thread overview]
Message-ID: <b4mmvehe6ai.fsf@jpl.org> (raw)
In-Reply-To: <b4mefzu1bh8.fsf@jpl.org>
On Mon, 23 Jan 2017 11:28:14 +0100, martin rudalics wrote:
> 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.
The main reason I use modify-frame-parameters is that a new frame
protrudes beyond the task-bar (placed at the bottom of the lower
screen) and so, I can't see the modeline and can't access the
mini-buffer on Cygwin, i.e.,
+----------------+
| +-------+ |
| | | |
| | Emacs | |
| | frame | |
| | | |
+----------------+
| Task-bar |
+----------------+
Possible solutions to help it would be to make the task-bar
hidden automatically, to shrink the height of a new Emacs frame
by some sort of means, or to move a new frame upward... Instead
of dragging it manually I use:
(defadvice make-frame (after adjust-frame-height-and-position activate)
"Shrink the height of a new frame and move it upward."
(if (ad-get-arg 0) nil
(sit-for 0) ;; Added for new Emacs 26
(modify-frame-parameters ad-return-value
'((height . 32) (top . 1112)))))
> Can you try this with a native Windows build and compare the behaviors?
Ok, I'll try the binary distribution.
> What does a specification like
> (make-frame '((left . (+ -8)) (top . (+ -32))))
> give here?
No difference with (make-frame). The new frame appears on
the lower screen, mode-line and minibuffer is hidden, and
`frame-parameters' shows:
((top . 1137) (left . 292) (width . 80) (height . 36))
next prev parent reply other threads:[~2017-01-23 22:54 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4mmvehe6ai.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=25511@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.