Re: test from TTS

[Drew Adams]

Mark Weaver, who's been posting my elisp files for me, sent your reply
on to me; I don't have newsgroup access, myself. 

Thanks for your feedback. Apparently my postings were not sufficiently
self-explanatory; I'm sure you're not the only one to wonder what's
going on. See my comments on your individual questions, below.

> -----Original Message-----
> From: address@hidden 
> [mailto:address@hidden
> Behalf Of Lars Clausen
> Sent: Wednesday, January 17, 2001 2:21 PM
> Subject: Re: autoload+.el - extensions to GNU `autoload.el'
> 
> Drew, you've been blasting these extensions out for a while 
> now.  Could you
> give us some idea of what the overall idea is?  Are there 
> some particular
> features you add to these packages?  Are your extensions 
> intended to be
> included in the original packages? 

The files README, DEPENDENCIES and DEPENDENCIES-EXPANDED, which I posted
earlier and which I'm also attaching to this email, should explain the
context (what I'm posting).

To add to what's said there:

1. The files are not all direct extensions of GNU Emacs. Some are
extensions of individual GNU Emacs source files (indicated by using the
same file name, with a + or - appended, before the ".el"). Others
provide new functionalities, but are not directly related to specific
GNU files. Still others (very few) are intended to replace the standard
GNU files with the same names.

2. The features added are described at the beginning of the
corresponding files.

3. I'm not sure what you mean by "the original packages". If you mean
the standard GNU distribution, then the answer is No; my code will not
be included automatically in an upcoming GNU release. I will no doubt
send a few of my files on to Gerd Moellmann at GNU to be considered for
ultimate inclusion in the standard distribution, but: a) someone (at
GNU) may have to rework a few things to make everything fit with the new
Emacs release (21), and b) it's better for individual folks out there in
Emacsland to first play with things I wrote, to determine for themselves
what's worthwhile and what's not so worthwhile.

I may soon be out of the loop (relatively inaccessible), so I'm offering
my code "as is" - people can do with it as they like. Hopefully, some of
the code will prove useful to someone, and hopefully that will be
improved by someone and perhaps integrated with the standard
distribution.

If you meant, instead, "is your code intended to work as is, when loaded
into a standard, virgin Emacs session", then the answer is Yes, that's
the intention - with the caveat that some files require some other files
in order to function properly. Those dependencies should be clearly
indicated at the start of the code in each file (via requires and
loads), and they are also all outlined in the (attached) files
DEPENDENCIES and DEPENDENCIES-EXPANDED.

 - Drew

README
Description: Text document

DEPENDENCIES
Description: Text document

DEPENDENCIES-EXPANDED
Description: Text document