From: martin rudalics <rudalics@gmx.at>
To: Philipp Stephani <p.stephani2@gmail.com>, 28189@debbugs.gnu.org
Subject: bug#28189: 26.0.50; Emacs uses deprecated function gtk_window_parse_geometry
Date: Wed, 23 Aug 2017 15:19:13 +0200 [thread overview]
Message-ID: <599D80D1.6090508@gmx.at> (raw)
In-Reply-To: <CAArVCkQEsxM6-9dFhNHbnN+ju+O24=1F5-DTiCb1ZsPD4E5e=g@mail.gmail.com>
> But doesn't removing the declaration break the build even if the function
> isn't called?
Sure. We can either remove x_gtk_use_window_move and call
gtk_window_move unconditionally or leave x_gtk_use_window_move alone and
call gtk_window_parse_geometry only if GTK_CHECK_VERSION permits it.
>> Can you build with unstable?
>>
>
> Haven't tried that (GTK appears to use a quite idiosyncratic build system),
> but the Emacs build already breaks on Debian testing when configuring with
> '--enable-gcc-warnings --enable-gtk-deprecation-warnings' (there are a few
> more deprecated functions that Emacs uses).
Have these already been deprecated with GTK 3.10.8? I'm using 3.4.2
here. In any case please post a list of these functions here (unless
you intend to take care of them by yourself).
Thanks, martin
next prev parent reply other threads:[~2017-08-23 13:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 20:22 bug#28189: 26.0.50; Emacs uses deprecated function gtk_window_parse_geometry Philipp
2017-08-23 8:46 ` martin rudalics
2017-08-23 10:38 ` Philipp Stephani
2017-08-23 13:19 ` martin rudalics [this message]
2017-08-23 23:26 ` Philipp Stephani
2017-08-24 9:37 ` martin rudalics
2017-08-25 9:28 ` Philipp Stephani
2017-08-26 9:29 ` martin rudalics
2017-08-27 13:34 ` Philipp Stephani
2017-09-03 11:49 ` martin rudalics
2017-09-19 15:35 ` Philipp Stephani
2017-09-19 16:38 ` Philipp Stephani
2017-09-23 11:22 ` Philipp Stephani
2017-09-23 13:21 ` martin rudalics
2017-09-23 13:28 ` Eli Zaretskii
2017-09-23 16:32 ` Philipp Stephani
2017-09-23 16:48 ` Eli Zaretskii
2017-09-23 18:28 ` martin rudalics
2017-09-23 18:31 ` Eli Zaretskii
2017-09-23 16:36 ` Philipp Stephani
2017-09-23 18:29 ` 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=599D80D1.6090508@gmx.at \
--to=rudalics@gmx.at \
--cc=28189@debbugs.gnu.org \
--cc=p.stephani2@gmail.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.