From: Sebastian Tennant <sebyte@smolny.plus.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Another 'best' practices question ??
Date: Fri, 04 May 2007 21:46:58 +0300 [thread overview]
Message-ID: <878xc41l5p.fsf@moley.org> (raw)
In-Reply-To: m3mz0kwlli.fsf@fleche.redhat.com
Quoth Tom Tromey <tromey@redhat.com>:
>>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
>
> Tom> Oops. That is fixed in the next release (I'll push it soon).
>
> Haha, I found what happened -- I released package.el 0.3 a while ago,
> but I neglected to upload it to ELPA. How ironic!
Don't let an oversight, however ironic, discourage you ;-)
> I've uploaded 0.3 now. The reported bug is fixed there.
>
> I haven't yet made it simple to upgrade package.el using itself. I'm
> considering adding that in a future version. Meanwhile you'll have to
> download package.el by hand and install it over the old copy. The
> direct link is:
>
> http://tromey.com/elpa/package.el
>
> ... but if you haven't yet installed package.el you probably should
> just use the auto-installer.
Now all is well. Updated the list, and installed (and played a game
of) sudoku without any problems. I haven't tried downloading games
from the net or anything like that yet.
Nice one geezer. (Yes, I'm from London).
I've no idea if this is of any interest to you but there were a couple
of warnings during compilation:
In get-board-wget:
sudoku.el:1258:18:Warning: reference to free variable `sudoku-wget-process'
In get-board-w3:
sudoku.el:1281:7:Warning: url-retrieve called with 1 argument, but requires 2-3
Regarding ELPA, a couple of suggestions if I may be so bold:
1. How about 'installed' rather than <blank> in the status column.
2. A hint as to how to run the newly installed package (not in the
description because there isn't room, but somewhere). For
instance, having installed sudoku in a snip, I then had to
navigate to the source file and read the commentary to find out
that I had to eval (require 'sudoku') before I was good to go.
3. 'g' in the Package buffer is described as 'revert'. Is this not
better described as 'refresh'?
Sebastian
next prev parent reply other threads:[~2007-05-04 18:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 17:47 Another 'best' practices question ?? William Case
2007-05-03 17:59 ` Lennart Borgman (gmail)
2007-05-03 19:35 ` William Case
2007-05-03 20:27 ` Lennart Borgman (gmail)
2007-05-04 6:12 ` Christian Herenz
2007-05-04 14:18 ` Tom Tromey
2007-05-04 15:23 ` Sebastian Tennant
2007-05-04 17:04 ` Tom Tromey
2007-05-04 17:21 ` Tom Tromey
2007-05-04 18:46 ` Sebastian Tennant [this message]
2007-05-04 18:41 ` Tom Tromey
2007-05-04 19:34 ` Sebastian Tennant
2007-10-29 12:29 ` ELPA package listings [formerly: Another 'best' practices question ??] Sebastian Tennant
2007-10-29 12:36 ` Sebastian Tennant
[not found] <mailman.183.1178214842.32220.help-gnu-emacs@gnu.org>
2007-05-04 16:36 ` Another 'best' practices question ?? Robert Thorpe
2007-05-04 18:24 ` Sebastian Tennant
2007-05-04 19:58 ` William Case
[not found] ` <mailman.256.1178309153.32220.help-gnu-emacs@gnu.org>
2007-05-08 13:40 ` Robert Thorpe
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=878xc41l5p.fsf@moley.org \
--to=sebyte@smolny.plus.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).