From: "Jan Djärv" <jan.h.d@swipnet.se>
To: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: --with-gtk as default?
Date: Wed, 28 Feb 2007 09:22:38 +0100 [thread overview]
Message-ID: <45E53BCE.4090300@swipnet.se> (raw)
In-Reply-To: <857iu267fm.fsf@lola.goethe.zz>
David Kastrup skrev:
> Richard Stallman <rms@gnu.org> writes:
>
>> Given that GNOME is considered part of the GNU project, should not 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?
Jan D.
next prev parent reply other threads:[~2007-02-28 8:22 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 19:43 --with-gtk as default? David Kastrup
2007-02-27 21:08 ` Eli Zaretskii
2007-02-27 21:20 ` David Kastrup
2007-02-27 21:27 ` Nick Roberts
2007-02-27 22:07 ` David Kastrup
2007-02-27 22:27 ` Nick Roberts
2007-02-27 22:30 ` David Kastrup
2007-02-27 22:13 ` David Kastrup
2007-02-27 22:21 ` David Kastrup
2007-02-28 4:28 ` Eli Zaretskii
2007-02-28 6:29 ` David Kastrup
2007-02-28 7:32 ` Jan Djärv
2007-02-28 20:43 ` Eli Zaretskii
2007-02-28 22:15 ` Jason Rumney
2007-03-01 4:20 ` Eli Zaretskii
2007-03-01 7:22 ` Jan Djärv
2007-03-01 8:44 ` Jason Rumney
2007-03-02 3:27 ` Richard Stallman
2007-03-02 7:40 ` Kevin Rodgers
2007-03-02 9:15 ` Jason Rumney
2007-03-02 13:43 ` Eli Zaretskii
2007-03-02 23:47 ` Richard Stallman
2007-03-02 23:46 ` Richard Stallman
2007-03-03 1:43 ` Jason Rumney
2007-03-04 2:00 ` Richard Stallman
2007-03-02 13:57 ` Eli Zaretskii
2007-02-28 20:32 ` Eli Zaretskii
2007-02-28 7:27 ` Richard Stallman
2007-02-28 7:57 ` David Kastrup
2007-02-28 8:22 ` Jan Djärv [this message]
2007-02-28 8:44 ` Nick Roberts
2007-02-28 8:48 ` David Kastrup
2007-02-28 11:23 ` Kim F. Storm
2007-02-28 11:40 ` David Kastrup
2007-02-28 12:18 ` Kim F. Storm
2007-02-28 12:28 ` David Kastrup
2007-02-28 13:00 ` Romain Francoise
2007-03-01 10:06 ` Nick Roberts
2007-03-01 11:45 ` Christian Faulhammer
2007-02-28 13:02 ` Andreas Schwab
2007-02-28 13:14 ` David Kastrup
2007-02-28 13:18 ` Andreas Schwab
2007-02-28 13:25 ` David Kastrup
2007-02-28 16:05 ` Stefan Monnier
2007-02-28 20:48 ` Eli Zaretskii
2007-03-01 9:07 ` David Kastrup
2007-03-01 1:09 ` Richard Stallman
2007-03-01 9:08 ` David Kastrup
2007-03-02 9:22 ` David Kastrup
2007-03-02 9:35 ` Jason Rumney
2007-03-02 9:45 ` David Kastrup
2007-03-02 10:57 ` Jan Djärv
2007-02-28 17:31 ` Ralf Angeli
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=45E53BCE.4090300@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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).