From: nljlistbox2@gmail.com (N. Jackson)
To: martin rudalics <rudalics@gmx.at>
Cc: 25851@debbugs.gnu.org
Subject: bug#25851: 25.2; GTK warning when starting Emacs when desktop file has more than one frame
Date: Mon, 27 Feb 2017 12:56:16 -0500 [thread overview]
Message-ID: <878torwm9r.fsf@moondust.localdomain> (raw)
In-Reply-To: <58B3DD98.6050701@gmx.at> (martin rudalics's message of "Mon, 27 Feb 2017 09:04:40 +0100")
At 09:04 +0100 on Monday 2017-02-27, martin rudalics wrote:
>
> Thanks. Please try now with a small init file containing a
> ‘make-frame’ call with the parameters from these attachments.
> For your first entry I'd suggest to start with bisecting the
> parameter list in calls like
>
> (make-frame
> '((font-backend xft x)
> (font . "-Bits-Bitstream Vera Sans Mono-normal-normal-normal-*-11-*-*-*-m-0-iso10646-1")
> (font-parameter)
> (border-width . 0)
> (internal-border-width . 0)
> (right-divider-width . 0)
> (bottom-divider-width . 0)
> (vertical-scroll-bars . right)
> (horizontal-scroll-bars)
> (foreground-color . "wheat")
> (background-color . "black")
> (mouse-color . "black")
> (border-color . "black")
> (screen-gamma)
> (line-spacing)
> (left-fringe . 8)
> (right-fringe . 0)
> (scroll-bar-foreground)
> (scroll-bar-background)
> (menu-bar-lines . 0)
> (tool-bar-lines . 0)
> (title)
> (wait-for-wm . t)
> (tool-bar-position . top)
> (icon-type . t)
> (auto-raise)
> (auto-lower)
> (cursor-type . box)
> (scroll-bar-width . 16)
> (scroll-bar-height . 0)
> (alpha)
> (fullscreen . fullboth)
> (display-type . color)
> (background-mode . dark)
> (cursor-color . "thistle")
> (visibility . t)
> (sticky)
> (frameset--id . "8B00-9439-83D1-B48B")
> (frameset--mini t)
> (modeline . t)
> (minibuffer . t)
> (unsplittable)
> (icon-name)
> (display . ":0")
> (explicit-name)
> (fullscreen-restore . maximized)
> (height . 59)
> (width . 191)
> (left . 0)
> (top . 0)))
>
From `emacs -Q' the above call to `make-frame' causes the GTK
warning message.
After bisecting, I find that if I omit the last two lines, the GTK
warning is not emitted. Either or both of these two lines is
sufficient to produce the warning message:
$ src/emacs -Q --eval "(make-frame '((left . 0)))"
(emacs:13000): Gtk-WARNING **: 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.
$ src/emacs -Q --eval "(make-frame '((top . 0)))"
(emacs:13008): Gtk-WARNING **: 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.
$ src/emacs -Q --eval "(make-frame '((left . 0)(top . 0)))"
(emacs:13020): Gtk-WARNING **: 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.
And finally,
$ src/emacs -Q --eval "(make-frame)"
produces no warning.
> IIUC you saved two frames. Please try whether you can reproduce the
> problem with one frame only. If not, you need two ‘make-frame’ calls.
There is no warning message issued for the first/main Emacs frame.
So there is one less warning message than there are frames
restored from the desktop file. So in my previous examples I had
three frames and two warning messages. I hope that helps clarify
things.
N.
next prev parent reply other threads:[~2017-02-27 17:56 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 16:08 bug#25851: 25.2; GTK warning when starting Emacs when desktop file has more than one frame N. Jackson
2017-02-23 16:24 ` Eli Zaretskii
2017-02-24 2:33 ` N. Jackson
2017-02-24 8:07 ` Eli Zaretskii
2017-02-24 13:41 ` N. Jackson
2017-02-24 13:53 ` N. Jackson
2017-02-24 14:10 ` Eli Zaretskii
2017-02-24 16:09 ` N. Jackson
2017-02-24 20:28 ` N. Jackson
2017-02-25 8:17 ` Eli Zaretskii
2017-02-26 22:41 ` N. Jackson
2017-02-27 0:31 ` N. Jackson
2017-02-27 16:18 ` Eli Zaretskii
2017-02-27 18:26 ` N. Jackson
2017-02-27 18:37 ` Eli Zaretskii
2017-02-28 9:46 ` martin rudalics
2017-03-01 20:05 ` N. Jackson
2017-03-23 8:00 ` martin rudalics
2017-03-23 14:11 ` N. Jackson
2017-03-24 9:01 ` martin rudalics
2017-03-24 20:28 ` N. Jackson
2017-03-25 6:26 ` Eli Zaretskii
2017-03-28 13:15 ` N. Jackson
2017-03-29 7:36 ` martin rudalics
2017-03-25 9:25 ` martin rudalics
2017-04-27 19:28 ` N. Jackson
2017-04-11 6:49 ` martin rudalics
2017-04-27 19:55 ` N. Jackson
2017-04-29 10:30 ` martin rudalics
2017-04-29 19:32 ` N. Jackson
2017-04-30 8:32 ` martin rudalics
2017-04-30 16:13 ` N. Jackson
2017-04-30 19:36 ` martin rudalics
2017-02-28 9:46 ` martin rudalics
2017-02-28 15:51 ` Eli Zaretskii
2017-02-28 18:42 ` martin rudalics
2017-02-28 18:50 ` Eli Zaretskii
2017-03-01 8:29 ` martin rudalics
2017-03-01 16:18 ` Eli Zaretskii
2017-03-01 19:36 ` martin rudalics
2017-03-01 19:47 ` Eli Zaretskii
2017-03-01 20:11 ` Eli Zaretskii
2017-03-02 11:00 ` martin rudalics
2017-03-02 15:09 ` Eli Zaretskii
2017-03-02 17:57 ` martin rudalics
2017-03-02 20:10 ` Eli Zaretskii
2017-03-03 8:13 ` martin rudalics
2017-03-03 8:25 ` Eli Zaretskii
2017-03-01 20:16 ` N. Jackson
2017-03-03 8:13 ` martin rudalics
2017-03-03 13:05 ` N. Jackson
2017-03-03 14:24 ` martin rudalics
2017-03-06 18:25 ` N. Jackson
2017-03-06 18:44 ` martin rudalics
2017-02-25 8:21 ` martin rudalics
2017-02-26 22:47 ` N. Jackson
2017-02-27 2:22 ` N. Jackson
2017-02-27 8:04 ` martin rudalics
2017-02-27 17:56 ` N. Jackson [this message]
2017-02-28 9:46 ` martin rudalics
2017-02-25 7:55 ` Eli Zaretskii
2017-02-26 22:09 ` N. Jackson
2017-03-23 7:59 ` martin rudalics
2017-03-23 13:47 ` Drew Adams
2017-03-23 14:34 ` N. Jackson
2017-03-24 9:01 ` martin rudalics
2017-03-24 20:37 ` N. Jackson
2017-03-25 9:25 ` martin rudalics
2017-03-23 15:24 ` Eli Zaretskii
2017-03-24 9:02 ` martin rudalics
2017-04-27 19:45 ` N. Jackson
2017-04-27 19:52 ` Noam Postavsky
2017-04-28 14:15 ` N. Jackson
2017-04-28 14:25 ` N. Jackson
2017-09-25 16:31 ` N. Jackson
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=878torwm9r.fsf@moondust.localdomain \
--to=nljlistbox2@gmail.com \
--cc=25851@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 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).