all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
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: Sat, 30 Sep 2017 00:05:20 +0300	[thread overview]
Message-ID: <838tgx5i7j.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkTTQPY-WkDdH_rDOmXFzBK2P-xohaKjxCrQhafnEzsSJA@mail.gmail.com> (message from Philipp Stephani on Fri, 29 Sep 2017 20:42:24 +0000)

> 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.

Or maybe we should ask the GTK developers not to delete them because
we need them?





  reply	other threads:[~2017-09-29 21:05 UTC|newest]

Thread overview: 10+ 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 [this message]
2017-09-29 21:42         ` Philipp Stephani
2017-09-29 21:57           ` [PATCH] Work around deprecation of gtk_style_context_get_background_color Philipp Stephani
2017-10-03 13:02             ` Philipp Stephani
2017-09-30  6:50           ` bug#28636: 27.0.50; Unable to load color "gtk_selection_bg_color" in 27.0.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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838tgx5i7j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28636@debbugs.gnu.org \
    --cc=aplanas@gmail.com \
    --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.