From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Removing unloaded functions from auto-mode-alist. Date: Tue, 26 Apr 2005 06:04:52 -0400 Message-ID: References: <87zmvu6ba2.fsf@xs4all.nl> <85ll7e68ei.fsf@lola.goethe.zz> <854qe2ihhi.fsf@lola.goethe.zz> <85oecagzwf.fsf@lola.goethe.zz> <874qdvc48k.fsf@xs4all.nl> <85fyxfrjal.fsf@lola.goethe.zz> <87is2balna.fsf@xs4all.nl> <857jirrg1f.fsf@lola.goethe.zz> <87br83wxuq.fsf@xs4all.nl> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1114509998 14775 80.91.229.2 (26 Apr 2005 10:06:38 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 26 Apr 2005 10:06:38 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 26 12:06:36 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DQMwy-00060w-7z for ged-emacs-devel@m.gmane.org; Tue, 26 Apr 2005 12:05:52 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DQN2e-0003CU-ME for ged-emacs-devel@m.gmane.org; Tue, 26 Apr 2005 06:11:44 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DQMye-00020l-Uv for emacs-devel@gnu.org; Tue, 26 Apr 2005 06:07:37 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DQMyd-00020F-V0 for emacs-devel@gnu.org; Tue, 26 Apr 2005 06:07:36 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DQMyd-0001ci-FL for emacs-devel@gnu.org; Tue, 26 Apr 2005 06:07:35 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DQN0R-0005Bf-L1 for emacs-devel@gnu.org; Tue, 26 Apr 2005 06:09:27 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1DQMw0-0001pm-Ky; Tue, 26 Apr 2005 06:04:52 -0400 Original-To: Lute Kamstra In-reply-to: <87br83wxuq.fsf@xs4all.nl> (message from Lute Kamstra on Mon, 25 Apr 2005 01:37:01 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:36400 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:36400 > 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.