At 14:47 02/12/98 +0100, Jan Vroonhof wrote:
Andy Piper <andyp(a)parallax.co.uk> writes:
> IMHO "Update Packages" should be on the main package menu as it is not
> specific to using packages with custom - its just a convenient way of
> getting the latest versions.
It is supposed to only update the package that were explicitly
selected using custom, see the doc string. However it really doesn't
do that now (to be more precise it just adds all the packages it can
find to the customize variables and then adds only those "selected").
That's what I put in the docstring, but it was a slight misnomer in that as
a side effect it updated installed packages to the latest version. As I
remember package-get-update-all didn't do this for some reason. I don't
really care which is called but I think you should be able to update all
your installed packages from the menubar (probably the most common thing
you would want to do over time) rather than go into a package manager of
some description.
1. what "Update Packages" does now is correct. However then
I do not
see the need to manage a whole set of packages using custom if you
are never going to use that set. Then using custom is just a bad
way of getting the menus and the "Manage Packages" menus should
simply use a menufilter and the "Using Custom" menu should be ditched.
Custom probably is a bad way although I think the effect is correct
(packages added / removed from the menubar). Although by that argument you
could argue that custom is bad period - custom is after all the standard
way of configuring emacs.
2. The Customize Packages system is really intented to manage an
orthogonal set of packages and the :initialize functions should be
ditched.
No the set should be the same.
andy
---------------------------------------------------------------------------
" .sigs are like your face - rarely seen by you and uglier than you think"
Dr Andy Piper, Technical Architect, Parallax Solutions Ltd
mail: andyp(a)parallax.co.uk web:
www.parallax.co.uk/~andyp