From: martin rudalics <rudalics@gmx.at>
To: emacs@martins.cc
Cc: 32207@debbugs.gnu.org
Subject: bug#32207: 26.1; can't set window position with emacs 26.3
Date: Wed, 25 Jul 2018 08:21:33 +0200 [thread overview]
Message-ID: <5B5816ED.2010702@gmx.at> (raw)
In-Reply-To: <17223.1532461092@monster.martins.cc>
> Compiled 25 and ran "emacs -Q -g ...'.
What are the -g specifications?
> It places the window
> fine, but ...
>
> Shell warnings:
> ---------------
> (emacs:23708): Gtk-WARNING **: 10:59:27.659:
> gtk_window_parse_geometry() called on a window with no
> visible children; the window should be set up before
> gtk_window_parse_geometry() is called.
This is to be expected (see Bug#25851 for further details) and should
have been solved for Emacs 26.
> Fvwm warnings (some duplicated for some reason):
> ------------------------------------------------
> [fvwm.0][__explain_placement]: placed new window 0x600122 'emacs@...':
> initial size 404x420
> desk 0 (current desk)
> current page
> position 400 400 (used user specified position)
>
> [fvwm.0][GetWindowSizeHints]: <<WARNING>> reason: 6: The hints have been ignored because the window's current size would have become invalid. The new hints will become active when the window generates the next ConfigureRequest.
>
> [fvwm.0][GetWindowSizeHints]: <<WARNING>> The application window (id 0x600122)
> "emacs@..." has broken size hints (inconsistent with current size).
> fvwm is ignoring those hints. hint override = 0, flags = 350
> min_width = 41, min_height = 84, max_width = 41, max_height = 84
> width_inc = 9, height_inc = 18
> min_aspect = 0/0, max_aspect = 0/0
> base_width = 41, base_height = 84
> win_gravity = 1
[...]
>
> Thus the position and size are fine, but it does generate a
> lot of warnings!
I have no idea what kind of "inconsistency" fvwm means here. It is
possible that 18 * 84 which gives 1512 pixels + 400 which gives 1912
pixels is too high for your screen.
Anyway, it seems that Emacs 25 while coming up with the intended
position/size does not behave correctly either. Let's do away with
-g and resources for the moment and try starting Emacs as follows:
emacs -Q --eval "(setq initial-frame-alist '((width . 41) (height . 84) (left . 400) (top . 400)))"
Do Emacs 25 and Emacs 26 behave differently and are there any
warnings?
Thanks, martin
next prev parent reply other threads:[~2018-07-25 6:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 23:41 bug#32207: 26.1; can't set window position with emacs 26.3 emacs
2018-07-19 8:20 ` martin rudalics
2018-07-19 13:26 ` emacs
2018-07-19 19:56 ` emacs
2018-07-20 6:42 ` martin rudalics
2018-07-20 20:10 ` Henrique Martins
2018-07-21 7:43 ` martin rudalics
2018-07-22 17:48 ` emacs
2018-07-23 6:51 ` martin rudalics
2018-07-24 19:38 ` emacs
2018-07-25 6:21 ` martin rudalics [this message]
2018-07-25 20:14 ` Henrique Martins
2018-07-26 7:56 ` martin rudalics
2018-07-26 19:36 ` emacs
2018-07-27 9:21 ` martin rudalics
2018-07-20 6:41 ` martin rudalics
2019-12-17 16:00 ` Elof Ofel
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=5B5816ED.2010702@gmx.at \
--to=rudalics@gmx.at \
--cc=32207@debbugs.gnu.org \
--cc=emacs@martins.cc \
/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).