unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca
Subject: Re: Removing unloaded functions from auto-mode-alist.
Date: Sat, 23 Apr 2005 23:00:57 +0200	[thread overview]
Message-ID: <87oec5p5rq.fsf@xs4all.nl> (raw)
In-Reply-To: <857jiucz6r.fsf@lola.goethe.zz> (David Kastrup's message of "Fri, 22 Apr 2005 22:51:40 +0200")

David Kastrup <dak@gnu.org> writes:

> Lute Kamstra <Lute.Kamstra.lists@xs4all.nl> writes:
>
>> Richard Stallman <rms@gnu.org> writes:
>>
>>>     Is there a reason why Fload can't do like do_autoload and use the
>>>     information recorded in Vautoload_queue to set the autoload property
>>>     of function symbols?
>>>
>>> Maybe it could work.
>>>
>>> I think it would be better not to try changing this now.
>>
>> Agreed; changing this would be tricky.  I'll put it on my post-release
>> todo list.  ;-)
>
> I have thought about it somewhat.  I have come to the opinion that it
> is a bad idea if load-file does this sort of recording since load-file
> is often used equivalently to eval-buffer and similar things.
>
> The function that _clearly_ should trigger/use the recorded
> information, however, is "require".

Agreed.

> I don't think we need to make (load "filename") (unload-feature
>'filename) do anything sensible (and indeed it is legal to load the
>same file several times in succession), but it seems desirable to
>have (require 'filename) (unload-feature 'filename) form a proper
>pair.

I'm not sure if it's the best solution not to let (load "filename")
record autoloads.  But letting only (require 'filename) record
autoloads would be a big improvement.  My guess is that the vast
majority of files get loaded by do_autoload and Frequire.
Furthermore, it seems quite easy to implement the recording of
autoloads in Frequire.  I'll give it a try and experiment with it for
a while...

> Unfortunately, this does not work well with the site-lisp.el construct 
> (mapc 'load-file (directory-files "site-start.d" t ".el\\'"))
>
> So a better expedient would be to have
> (provide 'xxx)
>
> turn on the necessary action at the end of the current load file in
> case that the feature is provided the first time.
>
> This should be a pretty reliable way to do the recordings for files
> that are connected with a "feature".

I'm not familiar with this.  Could you elaborate?

When is this used?  Does it load files that define functions that
replace autoloads?

Lute.

  reply	other threads:[~2005-04-23 21:00 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 15:23 Removing unloaded functions from auto-mode-alist Lute Kamstra
2005-04-19 16:25 ` David Kastrup
2005-04-19 17:44   ` Stefan Monnier
2005-04-19 21:28     ` David Kastrup
2005-04-19 21:58       ` Stefan Monnier
2005-04-19 22:33         ` David Kastrup
2005-04-20 18:52           ` Stefan Monnier
2005-04-24 20:24             ` Lute Kamstra
2005-04-24 20:50               ` David Kastrup
2005-04-24 21:51                 ` Lute Kamstra
2005-04-24 22:00                   ` David Kastrup
2005-04-24 23:37                     ` Lute Kamstra
2005-04-25  0:07                       ` David Kastrup
2005-04-26 10:04                       ` Richard Stallman
2005-04-20 19:22           ` Lute Kamstra
2005-04-19 23:01         ` Stefan Monnier
2005-04-19 23:14         ` Lute Kamstra
2005-04-19 23:24           ` David Kastrup
2005-04-20 18:41             ` Stefan Monnier
2005-04-20 19:00               ` David Kastrup
2005-04-20 19:18                 ` Stefan Monnier
2005-04-20 19:50                   ` David Kastrup
2005-04-20 19:29               ` Lute Kamstra
2005-04-20 14:57           ` Richard Stallman
2005-04-20 15:59             ` Lute Kamstra
2005-04-21 15:30               ` Richard Stallman
2005-04-21 16:35                 ` Lute Kamstra
2005-04-22 20:51                   ` David Kastrup
2005-04-23 21:00                     ` Lute Kamstra [this message]
2005-04-23 22:10                       ` David Kastrup
2005-04-24 20:21                         ` Lute Kamstra
2005-04-24 20:32                           ` David Kastrup
2005-04-24 20:52                             ` Lute Kamstra
2005-04-25 16:05                             ` Richard Stallman
2005-04-23 22:24                     ` Richard Stallman
2005-04-20 14:57         ` Richard Stallman
2005-04-20 15:02           ` Stefan Monnier
2005-04-20 15:57             ` David Kastrup
2005-04-20 18:37               ` Stefan Monnier
2005-04-20 19:19                 ` David Kastrup
2005-04-20 20:11                   ` Stefan Monnier
2005-04-20 20:25                     ` David Kastrup
2005-04-20 20:57                       ` Stefan Monnier
2005-04-20 21:33                         ` David Kastrup
2005-04-20 16:25             ` Andreas Schwab
2005-04-20 16:57               ` David Kastrup
2005-04-20 22:47                 ` Andreas Schwab
2005-04-20 22:58                   ` David Kastrup
2005-04-21  9:56                     ` Andreas Schwab
2005-04-21 10:12                       ` David Kastrup
2005-04-21 11:50                         ` Andreas Schwab
2005-04-21 19:56                         ` Richard Stallman
2005-04-21 20:13                           ` David Kastrup
2005-04-23 16:15                             ` Richard Stallman
2005-04-23 16:23                               ` David Kastrup
2005-04-23 16:15                           ` Richard Stallman
2005-04-21 11:41                       ` Johan Vromans
2005-04-20 15:43           ` David Kastrup
2005-04-21 15:30             ` Richard Stallman
2005-04-21 17:46               ` David Kastrup
2005-04-23 16:15                 ` Richard Stallman
2005-04-19 22:00       ` Lute Kamstra
2005-04-19 23:22       ` Andreas Schwab
2005-04-19 23:33         ` David Kastrup
2005-04-19 21:05   ` Lute Kamstra
2005-04-20 14:57     ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oec5p5rq.fsf@xs4all.nl \
    --to=lute.kamstra.lists@xs4all.nl \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).