Gnus development mailing list
 help / color / mirror / Atom feed
From: "Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov>
Cc: ding@gnus.org
Subject: Re: OFFTOPIC:  Where do you get your elisp?
Date: Tue, 3 Aug 1999 15:36:10 -0400 (EDT)	[thread overview]
Message-ID: <199908031936.PAA85527@alderaan.gsfc.nasa.gov> (raw)
In-Reply-To: <m3wvvcy9pk.fsf@knave.bfnet.com> (dave@bfnet.com)

I think the current state of elisp archiving is pretty sad. The elisp user
*and* developer communities badly need the equivalent of Perl's impressive
Comprehensive Perl Archive Network (or CPAN). 

To answer your question, I get my elisp almost exclusively from the
gnu.emacs.sources newsgroup, but I'm always missing articles since I don't
have time to read news as often as I would like and my news server expires
articles too quickly for my reading habits. (Does anyone know of a searchable
archive for gnu.emacs.sources on the Web?)

I see a lot of novice elisp developers implementing the same features that
others have implemented in the past. Countless times I have seen someone post
to gnu.emacs.sources some elisp code that they just spent days or weeks
writing only to have someone followup and tell them that somebody else wrote
the same thing two or more years ago. The result is that a lot of elisp
development energy is wasted because there is no good archive of elisp
packages! If elisp code isn't incorporated into Emacs (or XEmacs) at some
point, the code is often forgotten and dies, especially if the author doesn't
routinely post updates and/or continue enhancing it. I think it's a major
problem for the Emacs community, but nobody else seems to care.
Unfortunately, I don't have the time or resources to fix it.


  parent reply	other threads:[~1999-08-03 19:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-03 18:56 dave
1999-08-03 19:13 ` William M. Perry
1999-08-03 19:23   ` dave
1999-08-03 19:42     ` William M. Perry
1999-08-06  3:26       ` Greg Stark
1999-09-24 17:17         ` Lars Magne Ingebrigtsen
1999-08-03 19:28 ` Bill White
1999-08-03 19:36 ` Edward J. Sabol [this message]
1999-08-03 20:05   ` Bruce Stephens
1999-08-04  1:24   ` Jeremy D. Zawodny
1999-08-04  8:05     ` Kai Großjohann
     [not found]     ` <wtnoggoorr6.fsf@licia.dtek.chalmers.se>
1999-08-04 10:37       ` luis fernandes
1999-08-04 11:45         ` Felix Lee
1999-08-04 14:55         ` Edward J. Sabol
1999-08-04 16:13           ` Arcady Genkin
1999-08-05 13:50             ` Florian Weimer
1999-08-04 14:40       ` Randal L. Schwartz
1999-08-04 16:28         ` William M. Perry
1999-09-24 17:20     ` Lars Magne Ingebrigtsen
1999-08-04  9:05 ` Eric Marsden
1999-08-04 16:48   ` Colin Marquardt

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=199908031936.PAA85527@alderaan.gsfc.nasa.gov \
    --to=sabol@alderaan.gsfc.nasa.gov \
    --cc=ding@gnus.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).