From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: bug-gnu-emacs@gnu.org, rms@gnu.org
Subject: Re: the ...-unload-hook convention doesn't work
Date: Fri, 9 Jan 2004 11:08:34 -0600 (CST) [thread overview]
Message-ID: <200401091708.i09H8YU13964@raven.dms.auburn.edu> (raw)
In-Reply-To: <rzqhdz5w5iz.fsf@albion.dl.ac.uk> (message from Dave Love on Fri, 09 Jan 2004 14:39:00 +0000)
I can not but wonder what we exactly want to achieve with `unload-feature'.
Is there any hope of ever making it safe enough to be called in an
actual editing session in which non-trivial work is invested and will
_continue_ to be invested after unloading a feature? I do not believe
that it currently comes even remotely close to that standard.
The worst thing is that even reloading the feature often can not undo
the damage:
ELISP> (fboundp 'macroexpand)
t
ELISP> (require 'cl)
cl
ELISP> (fboundp 'macroexpand)
t
ELISP> (unload-feature 'cl) ;; Long output flushed
ELISP> (require 'cl)
cl
ELISP> (fboundp 'macroexpand)
nil
ELISP>
Sincerely,
Luc.
next prev parent reply other threads:[~2004-01-09 17:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 18:24 the ...-unload-hook convention doesn't work Luc Teirlinck
2004-01-06 14:33 ` Dave Love
2004-01-07 15:05 ` Richard Stallman
2004-01-09 14:39 ` Dave Love
2004-01-09 17:08 ` Luc Teirlinck [this message]
2004-01-11 19:37 ` Richard Stallman
2004-01-12 19:35 ` Kevin Rodgers
2004-01-16 0:23 ` Dave Love
[not found] ` <mailman.744.1074223463.928.bug-gnu-emacs@gnu.org>
2004-01-16 6:21 ` Simon Josefsson
2004-01-16 19:54 ` Richard Stallman
2004-01-17 2:22 ` Simon Josefsson
2004-01-17 0:21 ` Dave Love
2004-01-12 15:23 ` Dave Love
2004-01-11 19:36 ` Richard Stallman
2004-01-16 0:18 ` Dave Love
2004-01-16 19:54 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 15:01 Dave Love
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=200401091708.i09H8YU13964@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=bug-gnu-emacs@gnu.org \
--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).