From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
michael.albinus@gmx.de, 21440@debbugs.gnu.org, stefan@marxist.se
Subject: bug#21440: 25.0.50; Manual: FEATURE-unload-hook in (info "(elisp) Coding Conventions")
Date: Mon, 12 Jul 2021 14:05:13 +0200 [thread overview]
Message-ID: <87czrnu492.fsf@gnus.org> (raw)
In-Reply-To: <83y2abagjy.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Jul 2021 14:59:45 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> At least now (docstring of `unload-feature'):
>>
>> | If a function `FEATURE-unload-function' is defined, this function
>> | calls it with no arguments, before doing anything else. That function
>> | can do whatever is appropriate to undo the loading of the library. If
>> | `FEATURE-unload-function' returns non-nil, that suppresses the
>> | standard unloading of the library. Otherwise the standard unloading
>> | proceeds.
>>
>> So it can now be controlled whether standard unloading stuff will still
>> be performed (last problem mentioned in my report -> solved).
Ah, right.
>> This questionable paragraph is sill in the manual however:
>>
>> • If loading the file adds functions to hooks, define a function
>> ‘FEATURE-unload-function’, where FEATURE is the name of the feature
>> the package provides, and make it undo any such changes. Using
>> ‘unload-feature’ to unload the file will run this function. *Note
>> Unloading::.
>>
>> I guess it is a bit outdated and this had been automated long ago,
>> although partially heuristically.
>
> I don't understand why you say this is outdated. What did I miss?
>
>> Instead it could say what typical non-standard changes need to be
>> handled in an unload-function.
>
> Isn't that what it says?
Well, it recommends writing an unload function, although this is rarely
necessary. So it should say something about when it's necessary.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-07-12 12:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 11:43 bug#21440: 25.0.50; Manual: FEATURE-unload-hook in (info "(elisp) Coding Conventions") Michael Heerdegen
2020-08-15 13:53 ` Stefan Kangas
2020-08-17 11:15 ` Michael Albinus
2021-07-08 13:55 ` Lars Ingebrigtsen
2021-07-12 3:56 ` Michael Heerdegen
2021-07-12 11:59 ` Eli Zaretskii
2021-07-12 12:05 ` Lars Ingebrigtsen [this message]
2021-07-16 1:23 ` Michael Heerdegen
2021-07-16 9:01 ` Lars Ingebrigtsen
2021-07-17 1:21 ` Michael Heerdegen
2021-07-17 1:35 ` Michael Heerdegen
2021-07-17 14:08 ` Lars Ingebrigtsen
2021-07-21 2:45 ` Michael Heerdegen
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=87czrnu492.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21440@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=michael_heerdegen@web.de \
--cc=stefan@marxist.se \
/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).