From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: aplanas@gmail.com, 28636@debbugs.gnu.org
Subject: bug#28636: 27.0.50; Unable to load color "gtk_selection_bg_color" in 27.0.50
Date: Fri, 29 Sep 2017 21:42:28 +0000 [thread overview]
Message-ID: <CAArVCkRdb4Fn0rgqaEVmb4cdpg6sjLbaLUHB+YkZ-=QFnYJziQ@mail.gmail.com> (raw)
In-Reply-To: <838tgx5i7j.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Eli Zaretskii <eliz@gnu.org> schrieb am Fr., 29. Sep. 2017 um 23:05 Uhr:
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Fri, 29 Sep 2017 20:42:24 +0000
> >
> > Do you mean silencing the compiler warning? I guess so, but I think that
> would be a bit dangerous: at some
> > point the function might get removed entirely, then we'd have to
> scramble to find a replacement to keep the
> > code compilable, so I'd rather keep the compiler warning until we find a
> good solution.
>
> Do we have a reason to believe they will be removed any time soon?
> I've seen deprecated stuff kept for years on end.
>
GTK+ seems to be reasonably serious about this. The function in question
here is still present in the source code, but another one that we used to
call (gtk_window_parse_geometry) is already gone.
>
> Or maybe we should ask the GTK developers not to delete them because
> we need them?
>
We could, but I don't think that will have a high probability of success.
They would rightly point out that we're doing it wrong.
For the function in question, the definition is actually trivial, so we can
replace it with the definition for now to buy us some time.
[-- Attachment #2: Type: text/html, Size: 1746 bytes --]
next prev parent reply other threads:[~2017-09-29 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 20:05 bug#28636: 27.0.50; Unable to load color "gtk_selection_bg_color" in 27.0.50 aplanas
2017-09-28 20:22 ` Philipp Stephani
2017-09-29 8:34 ` martin rudalics
2017-09-29 20:42 ` Philipp Stephani
2017-09-29 21:05 ` Eli Zaretskii
2017-09-29 21:42 ` Philipp Stephani [this message]
2017-09-30 6:50 ` Eli Zaretskii
2017-09-29 20:44 ` Philipp Stephani
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='CAArVCkRdb4Fn0rgqaEVmb4cdpg6sjLbaLUHB+YkZ-=QFnYJziQ@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=28636@debbugs.gnu.org \
--cc=aplanas@gmail.com \
--cc=eliz@gnu.org \
/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).