From: Thomas L Roche <tlroche@us.ibm.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Mess with Emacs packages?
Date: Wed, 21 Mar 2007 20:50:08 -0400 [thread overview]
Message-ID: <OF0D7F8ADA.B354C5E1-ON852572A6.000319A6-852572A6.00049799@us.ibm.com> (raw)
In-Reply-To: <200703212316.l2LNGr0H027201@e4.ny.us.ibm.com>
Ignoramus16682 Wed, 21 Mar 2007 15:01:32 -0500
> is there a site that provides a good interface to getting a lot of
> packages.
http://www.emacswiki.org
is what there is. Package management is another problem: you might
want to investigate packages.el
http://lists.gnu.org/archive/html/gnu-emacs-sources/2007-03/msg00025.html
next parent reply other threads:[~2007-03-22 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703212316.l2LNGr0H027201@e4.ny.us.ibm.com>
2007-03-22 0:50 ` Thomas L Roche [this message]
2007-03-21 20:01 Mess with Emacs packages? Ignoramus16682
2007-03-21 20:04 ` Camille Bourgoin
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=OF0D7F8ADA.B354C5E1-ON852572A6.000319A6-852572A6.00049799@us.ibm.com \
--to=tlroche@us.ibm.com \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).