Re: change in Debian emacs policy: make global enabling of add-on lisp packages optional

2002-11-26 Thread D . Goel
> > Anyway, a good start would be to just report bugs against emacs add-on > packages that do something stupid (like those you mentioned). Fixing > those problems will help, regardless of whether some additional > mechanism is later added... Doing so. Thanks. (Had mailed all the package auth

Re: change in Debian emacs policy: make global enabling of add-on lisp packages optional

2002-11-26 Thread Peter S Galbraith
D.Goel <[EMAIL PROTECTED]> wrote: > > > > A typical emacs package has little effect unless you explicitly invoke it. > > While that is supposed to be true, it has been very untrue in > practice, IME. Here are some examples of the top of my head: > > * Installing maxima makes my emacs N new fun

Re: a2ps

2002-11-26 Thread Peter S Galbraith
Ian Zimmerman <[EMAIL PROTECTED]> wrote: > > Package a2ps places a pair of precompiled *.elc files (distributed > with the package) into /usr/share/emacs/site-lisp, instead of using > the emacsen-common framework to compile them. Is this a bug? I think > so, because the elc files are potentiall

Re: change in Debian emacs policy: make global enabling of add-on lisp packages optional

2002-11-26 Thread Miles Bader
"D. Goel" <[EMAIL PROTECTED]> writes: > While that is supposed to be true, it has been very untrue in > practice, IME. Here are some examples of the top of my head: > > * Installing maxima makes my emacs N new functinos with ~ N namespaces > * Installing ilisp makes emacs bind C-c which broke my

Re: change in Debian emacs policy: make global enabling of add-on lisp packages optional

2002-11-26 Thread Miles Bader
Faheem Mitha <[EMAIL PROTECTED]> writes: > Oh well, maybe I am trying to solve a problem which does not exist, > and it is not such a good idea after all. I'd been thinking about it > for a bit, and it did seem like a good one, though. I apologise for > troubling the members of the list. Well I pr

a2ps

2002-11-26 Thread Ian Zimmerman
Package a2ps places a pair of precompiled *.elc files (distributed with the package) into /usr/share/emacs/site-lisp, instead of using the emacsen-common framework to compile them. Is this a bug? I think so, because the elc files are potentially broken on emacsen other than the one that compiled

Re: change in Debian emacs policy: make global enabling of add-on lisp packages optional

2002-11-26 Thread D . Goel
> > A typical emacs package has little effect unless you explicitly invoke it. While that is supposed to be true, it has been very untrue in practice, IME. Here are some examples of the top of my head: * Installing maxima makes my emacs N new functinos with ~ N namespaces, and N is very large.

Re: change in Debian emacs policy: make global enabling of add-on lisp packages optional

2002-11-26 Thread Faheem Mitha
On Tue, 26 Nov 2002 15:10:15 -0500, Miles Bader <[EMAIL PROTECTED]> wrote: > On Tue, Nov 26, 2002 at 06:05:26PM +, Faheem Mitha wrote: >> I think that for add-on lisp packages for emacs, there should be an >> install-time option (debconf would be the obvious way to go here) to >> enable the pac

Re: change in Debian emacs policy: make global enabling of add-on lisp packages optional

2002-11-26 Thread Miles Bader
On Tue, Nov 26, 2002 at 06:05:26PM +, Faheem Mitha wrote: > I think that for add-on lisp packages for emacs, there should be an > install-time option (debconf would be the obvious way to go here) to > enable the package globally, and if it is not enabled globally, there > should be instructions

change in Debian emacs policy: make global enabling of add-on lisp packages optional

2002-11-26 Thread Faheem Mitha
Dear People, I don't know if I am out of line here, I'm not a Debian Developer or a maintainer of an emacs-related package, just an appreciative user. I think that for add-on lisp packages for emacs, there should be an install-time option (debconf would be the obvious way to go here) to enable th