From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Removing unloaded functions from auto-mode-alist.
Date: Wed, 20 Apr 2005 10:57:15 -0400 [thread overview]
Message-ID: <E1DOGdf-0004Yi-O1@fencepost.gnu.org> (raw)
In-Reply-To: <87wtqy4gvv.fsf@xs4all.nl> (message from Lute Kamstra on Tue, 19 Apr 2005 23:05:08 +0200)
I guess it can't hurt to leave a function on a hook or in
auto-mode-alist if it is replaced by a restored autoload. (Even if
feature x actually put it there.) See patch below. Erring on the
other side seems more damaging: removing a function from a hook when
that function was put there by a user's init file or something.
Usually when a package defines a function and puts it on hooks, that
function will not be autoloaded. If the function is autoloaded, that
means it is meant to be used when the package is not loaded. So that
function might be put on hooks by users before the package is loaded.
So I think what you're proposing is the right criterion.
It would be right most of the time.
prev parent reply other threads:[~2005-04-20 14:57 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
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 [this message]
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=E1DOGdf-0004Yi-O1@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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).