From: Ivan Shmakov <ivan@siamics.net>
To: 22243@debbugs.gnu.org
Subject: bug#22243: eieio-opt: not quite (?) optional functions
Date: Sat, 26 Dec 2015 13:00:45 +0000 [thread overview]
Message-ID: <87wps1xt36.fsf@violet.siamics.net> (raw)
Package: emacs
Severity: wishlist
eieio.el currently (1dcf9a5d2a72; 2015-12-22 17:02:30 UTC)
reads:
943 ;; Hook ourselves into help system for describing classes and methods.
944 ;; FIXME: This is not actually needed any more since we can click on the
945 ;; hyperlink from the constructor's docstring to see the type definition.
946 (add-hook 'help-fns-describe-function-functions 'eieio-help-constructor)
This results that with -Q, 'eieio-opt gets loaded immediately
once the user tries to use the Emacs help system (say, C-h f),
making the file’s description (below) somewhat misleading, as
the library which is hooked into such a basic Emacs facility
could hardly be called “optional”.
;;; eieio-opt.el -- eieio optional functions (debug, printing, speedbar)
I don’t think I deal much with EIEIO objects, but I’ve removed
the function from the hook (below) quite some time ago and seen
no adverse effects so far. Hence, I guess the add-hook above
may be reconsidered (per its own FIXME notice.)
(remove-hook 'help-fns-describe-function-functions
'eieio-help-constructor)
As an aside, I’ve spotted this issue because eieio-opt depends
on 'speedbar, which I’ve become aware of a decade ago, and still
have found no use for; thus anything dependent on it immediately
raises my suspicion.
--
FSF associate member #7257 http://am-1.org/~ivan/ … 3013 B6A0 230E 334A
next reply other threads:[~2015-12-26 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 13:00 Ivan Shmakov [this message]
2019-08-01 17:09 ` bug#22243: eieio-opt: not quite (?) optional functions Lars Ingebrigtsen
2019-08-01 17:33 ` Noam Postavsky
2019-08-01 17:37 ` Lars Ingebrigtsen
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=87wps1xt36.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=22243@debbugs.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).