unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Dan Nicolaescu <dann@gnu.org>,
	"6505@debbugs.gnu.org" <6505@debbugs.gnu.org>
Subject: bug#6505: make the Gtk+ port compile with -DGSEAL_ENABLE in	preparation for Gtk+-3
Date: Sun, 27 Jun 2010 13:56:26 -0400	[thread overview]
Message-ID: <8739w84awl.fsf@stupidchicken.com> (raw)
In-Reply-To: <85A9396B-8B71-4F9B-9281-8F2B90BCBE97@swipnet.se> ("Jan Djärv"'s message of "Sat, 26 Jun 2010 00:43:32 +0200")

Jan Djärv <jan.h.d@swipnet.se> writes:

> 25 jun 2010 kl. 23:42 skrev Dan Nicolaescu <dann@gnu.org>:
>
>> Good to hear you already have some solution.
>> IMHO the main thing is that emacs should not be seen as lagging
>> behind.  When the first distribution switches to version 3, it would be
>> good to have something available...
>
> I we must see a Gnome based on Gtk 3.0 first. It is not possible
> (without #ifdefs) to support < 2.14 and 3.0.
>
> If it is just a few ifdefs I will add them.  But we need to decide if
> configure should start to check for Gtk 3.0. Maybe now is the time.

Yes, I think bumping the requirement to 2.14 in the trunk is fine, as is
adding support for 3.0, provided it does not interfere with the GTK-2
support.  Thanks for working ahead on this.





  reply	other threads:[~2010-06-27 17:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24 18:34 bug#6505: make the Gtk+ port compile with -DGSEAL_ENABLE in preparation for Gtk+-3 Dan Nicolaescu
2010-06-25 13:50 ` Jan Djärv
2010-06-25 21:02   ` Glenn Morris
2010-06-25 22:47     ` Jan Djärv
2010-06-25 21:42   ` Dan Nicolaescu
2010-06-25 22:43     ` Jan Djärv
2010-06-27 17:56       ` Chong Yidong [this message]
2010-06-28  7:03         ` Yavor Doganov
2010-06-28 10:19           ` Jan Djärv

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=8739w84awl.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=6505@debbugs.gnu.org \
    --cc=dann@gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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).