Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
Subject: Re: How many use eMacs and Gnus on daily basis?
Date: Thu, 08 Jun 2006 20:33:00 +0200	[thread overview]
Message-ID: <854pyv1orn.fsf@lola.goethe.zz> (raw)
In-Reply-To: <PoidnYxR4pun-BXZnZ2dnUVZ_t-dnZ2d@comcast.com>

notbob <notbob@nothome.com> writes:

> On 2006-06-08, David Z Maze <dmaze@mit.edu> wrote:
>
>> 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;........
>
> Well, it used to.  No longer.  Now all those packages must be added
> by the user.  I recently downloaded and compiled xemacs only to
> discover basic functions like calendar, gnus, and dired are not
> included.
>
> I found this disclaier:
>
> " In order to reduce the size and increase the maintainability of
> XEmacs, the majority of the Elisp that came with previous releases
> have been unbundled."

Well, but they do provide the "sumo tarballs".  In principle, this
should allow components of XEmacs be updated independently in a more
timely manner.  In practice, it seems to rather have the effect of
developers not being worried about components getting outdated
independently.

At least XEmacs manages quite more frequent releases and partial
updates than Emacs does, but with mixed quality.  Arguably the XEmacs
development and release process scales quite better to the number of
active developers.  Unfortunately, developers are a scarce resource
for both Emacsen.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2006-06-08 18:33 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
2006-06-08 14:57       ` David Kastrup
2006-06-08 17:58       ` notbob
2006-06-08 18:33         ` David Kastrup [this message]
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=854pyv1orn.fsf@lola.goethe.zz \
    --to=dak@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.
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).