Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David Z Maze <dmaze@mit.edu>
Subject: Re: How many use eMacs and Gnus on daily basis?
Date: Thu, 08 Jun 2006 10:30:21 -0400	[thread overview]
Message-ID: <y688xo74t4y.fsf@contents-vnder-pressvre.mit.edu> (raw)
In-Reply-To: <2r4f82pi5bsuiv9qfkacrs6hej6iva56u9@4ax.com>

me@privacy.net writes:

> Now is this plain eMacs?
>
> Isn't there something called Xemacs as well?

"Same thing, but different."  If memory serves, XEmacs started life as
a branch from "normal" ("FSF" or "GNU") Emacs over frustration on
getting one of the older releases out.  It's historically had a little
better support for inlined images, proportional fonts, and the like,
at the cost of supporting those features differently from "normal"
Emacs when it's added them in as well.  XEmacs's other advantage is
that it comes with an add-on bundle of approximately every elisp
package out there; "normal" Emacs is much more conservative about what
can be included (due to likely-justified license paranoia: while people
complain about the Linux kernel being of dubious heritage, all code
distributed with Emacs has had copyright assigned to the FSF).

My current feel is that XEmacs doesn't offer a whole lot that's not in
Emacs, and my normal environment makes it a little easier to use
Emacs.  Gnus supports both fine, including adapting to whichever emacs
is currently being used.

  --dzm [hoping he used the correct terminology to refer to the emacsen]

  reply	other threads:[~2006-06-08 14:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 14:34 me
2006-06-07 14:41 ` Hadron Quark
2006-06-07 15:05   ` me
2006-06-07 15:19     ` Hadron Quark
2006-06-07 15:40     ` Mark T.B. Carroll
2006-06-09  8:17       ` Tim X
2006-06-09  9:46         ` rambam
2006-06-07 15:46     ` Ted Zlatanov
2006-06-07 15:46     ` Malte Spiess
2006-06-09  8:13     ` Tim X
2006-06-09 13:49       ` me
2006-06-07 14:50 ` Mark T.B. Carroll
2006-06-07 15:48 ` David Z Maze
2006-06-07 15:49 ` Robert D. Crawford
2006-06-07 17:49   ` notbob
2006-06-08  8:09     ` Glyn Millington
2006-06-10  6:41   ` Joe Bush
2006-06-10  9:17     ` Tim X
2006-06-10 20:01     ` Robert D. Crawford
2006-06-12 17:27       ` Joe Bush
2006-06-08  0:57 ` Joe Fineman
2006-06-08  1:17   ` Bastien
2006-06-08  1:40   ` Johan Bockgård
2006-06-08  6:18     ` David Kastrup
2006-06-08  1:59   ` Robert D. Crawford
2006-06-08  3:03   ` me
2006-06-08 14:30     ` David Z Maze [this message]
2006-06-08 14:57       ` David Kastrup
2006-06-08 17:58       ` notbob
2006-06-08 18:33         ` David Kastrup
2006-06-08 14:46     ` Eric Eide
2006-06-09  8:27   ` Tim X

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=y688xo74t4y.fsf@contents-vnder-pressvre.mit.edu \
    --to=dmaze@mit.edu \
    /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 NNTP newsgroup(s).