From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?ISO-8859-1?Q?Jan_Dj=E4rv?= Newsgroups: gmane.emacs.devel Subject: Re: --with-gtk as default? Date: Fri, 02 Mar 2007 11:57:41 +0100 Message-ID: <45E80325.6050509@swipnet.se> References: <85wt23idxi.fsf@lola.goethe.zz> <857iu267fm.fsf@lola.goethe.zz> <45E53BCE.4090300@swipnet.se> <85abyw9ezt.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1172833127 3416 80.91.229.12 (2 Mar 2007 10:58:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 2 Mar 2007 10:58:47 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 02 11:58:38 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HN5TB-0004nr-FN for ged-emacs-devel@m.gmane.org; Fri, 02 Mar 2007 11:58:37 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HN5TB-0001e3-2v for ged-emacs-devel@m.gmane.org; Fri, 02 Mar 2007 05:58:37 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HN5Sx-0001d0-B4 for emacs-devel@gnu.org; Fri, 02 Mar 2007 05:58:23 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HN5Sv-0001cb-P7 for emacs-devel@gnu.org; Fri, 02 Mar 2007 05:58:22 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HN5Sv-0001cW-FR for emacs-devel@gnu.org; Fri, 02 Mar 2007 05:58:21 -0500 Original-Received: from av10-1-sn2.hy.skanova.net ([81.228.8.181]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HN5Su-0008GV-DT for emacs-devel@gnu.org; Fri, 02 Mar 2007 05:58:20 -0500 Original-Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502) id 7D12237FC1; Fri, 2 Mar 2007 11:58:13 +0100 (CET) Original-Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP id 61FAC37E42; Fri, 2 Mar 2007 11:58:13 +0100 (CET) Original-Received: from husetbladh.homeip.net (81-235-205-78-no59.tbcn.telia.com [81.235.205.78]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 45B9E37E44; Fri, 2 Mar 2007 11:58:12 +0100 (CET) User-Agent: Thunderbird 1.5.0.9 (X11/20070212) In-Reply-To: <85abyw9ezt.fsf@lola.goethe.zz> X-detected-kernel: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:67217 Archived-At: David Kastrup skrev: > Jan Dj=E4rv writes: >=20 >> David Kastrup skrev: >>> Richard Stallman writes: >>> >>>> Given that GNOME is considered part of the GNU project, should n= ot be >>>> --with-gtk be the default for compiling Emacs rather than Athena >>>> widgets, at least where GTK+ is available? >>>> >>>> In principle maybe, but it isn't working well enough yet. >>> Interesting. In my experience, it is working quite better than the >>> Athena widgets. Which is one of the reasons I have been using the >>> Gtk+ port for years now. For example, it has no problems using >>> Unicode in the menus. >>> >>> Could you provide examples about things that work worse than with >>> Athena widgets? >> The only thing I can think of is the display close bug that Gtk+ >> has. Are there other problems that keeps us from having --with-gtk >> as the default? >=20 > As far as I remember from the discussions (and I might well be wrong), > the display close bug has been fixed in the newest Gtk+ versions. Well, sortof. There are still memoty leaks inside Gtk+, but it does not = crash. >=20 > So how would this strategy be? If no toolkit is specified and GTK+ is > available, use GTK+ if it does not crash on display close. >=20 > Of course, at configure time, we might not have a DISPLAY available in > the first place. Is there a good heuristic to figure out whether a > given GTK+ version would crash on close, even without having a display > in the first place to test it with? >=20 In gtkutil.c we just check that Gtk+ is version 2.10 or newer. Jan D.