all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: help-gnu-emacs@gnu.org
Cc: Eric Lindblad <lindblad@gmx.com>
Subject: Re: gtk2/gtk3
Date: Tue, 18 Dec 2018 20:38:19 +0100	[thread overview]
Message-ID: <8736qur5g4.fsf@telefonica.net> (raw)
In-Reply-To: trinity-a55630e0-42e5-41ce-a88b-ce91c80e77f1-1545157179275@3c-app-mailcom-bs11

"Eric Lindblad" <lindblad@gmx.com> writes:

>    from emacs-26.1 maybe this is just outdated configure script content
>
>    either of '--with-x-toolkit=gtk2' or '--with-x-toolkit=gtk3' produce
>    this shell output
>
>    configure: WARNING: Your version of Gtk+ will have problems with
>    closing open displays.  This is no problem if you just use
>    one display, but if you use more than one and close one of them
>    Emacs may crash.
>
>    what the following from bugzilla [dot] gnome [dot] org/show_bug [dot]
>    cgi?id=85715
>
>    is supposed to mean is unclear
>
>    Status: RESOLVED OBSOLETE
>
>    the emacs-26.1 configure script (near line 12500) is were the warning
>    is written
>
>    if this was attended to, i.e., no longer an issue, perhaps the
>    configure script should be updated
>
>    or please inform if it is still an issue for gtk2 and gtk3

This is still an issue. Apparently Gnome migrated to gitlab and the bug
report on the previous system was automatically closed. The second last
message on that report points to

https://gitlab.gnome.org/GNOME/gtk/issues/221

Maybe the configure script should be updated to mention that URL. Please
file a bug report (M-x report-emacs-bug) to request that change.




  reply	other threads:[~2018-12-18 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 18:19 gtk2/gtk3 Eric Lindblad
2018-12-18 19:38 ` Óscar Fuentes [this message]
2018-12-19 12:38   ` gtk2/gtk3 Noam Postavsky

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=8736qur5g4.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=help-gnu-emacs@gnu.org \
    --cc=lindblad@gmx.com \
    /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.