all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: storm@cua.dk (Kim F. Storm)
Cc: "Nick Roberts" <nickrob@snap.net.nz>,
	"Jan Djärv" <jan.h.d@swipnet.se>,
	rms@gnu.org, emacs-devel@gnu.org
Subject: Re: --with-gtk as default?
Date: Wed, 28 Feb 2007 13:28:25 +0100	[thread overview]
Message-ID: <85mz2ympp2.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3ps7uh3vc.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Wed\, 28 Feb 2007 13\:18\:47 +0100")

storm@cua.dk (Kim F. Storm) writes:

> David Kastrup <dak@gnu.org> writes:
>
>> Sigh.  So the default Emacs installations for decades to come are
>> going to show off the utterly archaic Athena look, 
>
> hgiS.  I happen to like that look (but maybe I look a bit archaic myself).

It does not blend into current desktops at all.  Which is the greatest
weakness of XEmacs' looks IMO (it looks pretty much the same on every
desktop, and pretty much out of kilter everywhere).

So we get well-integrated looks supporting antialiased Unicode menus
under Windows and MacOSX desktops by default, and a bunch of rather
crudely designed retrowidgets (and no "open file" widgets at all IIRC)
with pixelish menu fonts under GNU/Linux and other X11 based desktops.

Such a waste.  It's frustrating to advertise an editor that visually
appears to be stuck in the last millennium.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-02-28 12:28 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=85mz2ympp2.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=nickrob@snap.net.nz \
    --cc=rms@gnu.org \
    --cc=storm@cua.dk \
    /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.