Re: Removing unloaded functions from auto-mode-alist.

[Richard Stallman <rms@gnu.org>]

    > But it is very common that one loads and evals one and the same file
    > over and over.  We don't want to keep a history of that.

    I had not considered that.  Does loading the same file more than once
    really happen often?  On purpose?  For what reason?

To load a file multiple times is fairly common when one is changing
and debugging the file.  It would be good if this did not fool
unload-feature.

I don't think unload-feature should try to handle strange practices
where a file redefines things that come from some other file.  If we
don't try to handle that, it should not be terribly hard to avoid
confusion when a tame and clean file is loaded more than once.

    Well, I still think that when we are concerned about a working
    unload-feature, the decisive criterion is that we want to be able to
    restore the state before a load that actually first provided a
    feature, and it does not really matter whether this load was initiated
    by load, by an autoload, or by require.

I agree with that.  If a file is well-behaved, unload-feature should
handle unloading it regardless of how the file was loaded.
That should not be too hard.