From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: stefan@marxist.se, michael.albinus@gmx.de, 21440@debbugs.gnu.org
Subject: bug#21440: 25.0.50; Manual: FEATURE-unload-hook in (info "(elisp) Coding Conventions")
Date: Fri, 16 Jul 2021 11:01:43 +0200 [thread overview]
Message-ID: <87o8b2d43s.fsf@gnus.org> (raw)
In-Reply-To: <87zgunuk5n.fsf@web.de> (Michael Heerdegen's message of "Fri, 16 Jul 2021 03:23:00 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
>> Well, it recommends writing an unload function, although this is rarely
>> necessary. So it should say something about when it's necessary.
>
> Yes, exactly.
I've now clarified that section...
> The second paragraph of `unload-feature' has some good examples
... but I don't think we need to go into details about what
unload-feature does in the Coding Conventions section in the manual.
> (should we add advices to that list btw?).
Hm... does unload-feature remove advices? Let's see..
Well, there's this:
(defun loadhist--unload-function (x)
(let ((fun (cdr x)))
(when (fboundp fun)
(when (fboundp 'ad-unadvise)
(ad-unadvise fun))
Hm... but is that what it does?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-07-16 9:01 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
2021-07-16 1:23 ` Michael Heerdegen
2021-07-16 9:01 ` Lars Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8b2d43s.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21440@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.