From: Hendrik Sattler <sattler2000@gmx.de>
Subject: Re: Compiling Emacs with GTK
Date: Sat, 26 Feb 2005 01:49:07 +0100 [thread overview]
Message-ID: <cvoh22$m8a$02$2@news.t-online.com> (raw)
In-Reply-To: mailman.1721.1109377814.32256.help-gnu-emacs@gnu.org
nfreimann wrote:
> --- August <fusionfive@comhem.se> schrieb:
>
>> With "the standard Emacs release" I mean the non-CVS
>> version. Will this
>> GUI support make it to the next release?
>
> cvs emacs offers gkt and advanced windows support
> since more than an year. Therefore I wonder that the
> new 21.4 does not support gtk. Clearly spoken, emacs
> without gkt and advanced windows support is outdated.
> Its looks anachronistic and behaves crippled in linux
> as well as in windows.
>
> There is a excellent windows binary cvs emacs
> distribution available at
> http://nqmacs.sourceforge.net/. Its the best windows
> emacs ever. Why not supporting a binary cvs gtk2-emacs
> for linux at ftp.gnu or sourceforge.net? Whats the
> problem with that?
According to
http://savannah.gnu.org/cgi-bin/viewcvs/emacs/emacs/etc/NEWS?rev=1.1120&content-type=text/vnd.viewcvs-markup
this is left to emacs-22.
I am just wondering, why they mention emacs-22.1 there, I don't remember an
emacs-22.0
HS
next parent reply other threads:[~2005-02-26 0:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1721.1109377814.32256.help-gnu-emacs@gnu.org>
2005-02-26 0:49 ` Hendrik Sattler [this message]
2005-02-26 1:17 ` Compiling Emacs with GTK David Kastrup
2005-02-26 1:57 ` August
[not found] ` <mailman.1728.1109384621.32256.help-gnu-emacs@gnu.org>
2005-02-26 2:58 ` David Kastrup
[not found] ` <cvugmg$4ks$1@news.sap-ag.de>
2005-02-28 17:13 ` Kevin Rodgers
2005-02-26 1:12 ` David Kastrup
[not found] <mailman.1362.1109200883.32256.help-gnu-emacs@gnu.org>
2005-02-23 23:26 ` David Kastrup
2005-02-24 0:44 ` August
2005-02-24 10:25 ` Peter Dyballa
2005-02-24 15:07 ` August
[not found] ` <mailman.1374.1109208216.32256.help-gnu-emacs@gnu.org>
2005-02-24 8:12 ` Hendrik Sattler
2005-02-24 11:33 ` David Kastrup
2005-02-24 11:49 ` Hendrik Sattler
2005-02-24 12:12 ` David Kastrup
2005-02-24 14:37 ` Hendrik Sattler
2005-02-24 14:58 ` David Kastrup
2005-02-24 15:22 ` Lee Sau Dan
2005-02-24 15:53 ` Hendrik Sattler
2005-03-16 17:02 ` David Combs
2005-03-16 17:46 ` Stefan Monnier
2005-03-16 18:48 ` Kevin Rodgers
2005-02-25 13:46 ` Stefan Monnier
2005-02-25 14:18 ` David Kastrup
2005-02-25 17:50 ` August
[not found] ` <mailman.1673.1109355702.32256.help-gnu-emacs@gnu.org>
2005-02-25 18:36 ` David Kastrup
2005-02-25 23:28 ` August
2005-02-26 0:13 ` nfreimann
2005-02-26 1:40 ` August
2005-02-26 13:29 ` Eli Zaretskii
[not found] ` <mailman.1725.1109384617.32256.help-gnu-emacs@gnu.org>
2005-02-26 8:22 ` Thien-Thi Nguyen
2005-02-26 13:23 ` Eli Zaretskii
2005-02-26 15:09 ` nfreimann
2005-02-26 16:02 ` Eli Zaretskii
2005-02-26 15:06 ` David Hansen
2005-02-26 16:05 ` nfreimann
[not found] ` <mailman.1792.1109435067.32256.help-gnu-emacs@gnu.org>
2005-02-26 16:38 ` David Hansen
2005-02-26 17:02 ` David Kastrup
[not found] ` <mailman.1777.1109425933.32256.help-gnu-emacs@gnu.org>
2005-02-26 19:40 ` Stefan Daschek
2005-02-23 23:01 August
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='cvoh22$m8a$02$2@news.t-online.com' \
--to=sattler2000@gmx.de \
/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.
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).