Re: It's Huntin' Season
>>"Thomas" == Thomas Bushnell, BSG <email@example.com> writes:
Thomas> Manoj Srivastava <firstname.lastname@example.org> writes:
>> If they are merely programs, why are they being invoked at
>> startup? I would posit that the ``program'' part of the file belongs
>> in with the package propoer, and the invocation, which can be
>> overridden is the only thing that should be in /etc/emacs*/site-start.d
Thomas> It's not invoked at all in site-start.d. If it were, then of course,
Thomas> that would be configuration information.
Thomas> I'm thinking about the ones that invoke the program, but
Thomas> instead, merely make its commands available. A typical
Should not be in site-start.d at all. They should be in
Thomas> example would set a few variables (pointing it at Debian
Thomas> locations for things, the sort of thing that would be
Thomas> specified at compile time for a binary), and then set some
These are configuration settings.
Thomas> autoloads (the equivalent of putting the binaries into /bin).
Nope. This is part of what I mentioned about maintainers not
knowing fully the circumstances packages are used in. I may want to
use Debian packaged bbd, for example, but I have my 3leet bbdb-com.el
(called, of course, 3leet-bbdb-com.el).
I would say that not being able to selectively over ride the
autoloads for the functions in bbdb-com.el to my own versions is a
Even autoloads are configurable settings.
System going down at 1:45 this afternoon for disk crashing.
Manoj Srivastava <email@example.com> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C