> I see the .el file is now is lisp/obsolete where it does not get installed
    > by default,

    It does get installed.  And it is autoloaded.

Actually, I think it isn't.  This is because of the change we made
a couple of months ago not to scan the `obsolete' directory for
autoloads.

It's possible that that change was a mistake.

However, I think there were real problems (at some point) of conflicts
caused by autoloaded functions in obsolete files that had the same
names as autoloaded functions in non-obsolete files.  Thus, if we
don't scan `obsolete' for autoloads, we can simply move the old file
to `obsolete' without changing it.  If we do scan `obsolete' for
autoloads, we have to remember to delete its autoloads when necessary.

So we have three solutions:

1. Move lazy-lock back out of `obsolete'.

2. Reenable scanning of `obsolete' for autoloads.

3. Tell people "you must explicitly load `obsolete/lazy-lock'
if you want to keep using it, and let the error message serve
to remind people to switch.

What do people think about them?


_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

Reply via email to