unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ivan Shmakov <ivan@siamics.net>
Cc: 22243@debbugs.gnu.org
Subject: bug#22243: eieio-opt: not quite (?) optional functions
Date: Thu, 01 Aug 2019 19:09:26 +0200	[thread overview]
Message-ID: <87d0hoke2h.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87wps1xt36.fsf@violet.siamics.net> (Ivan Shmakov's message of "Sat, 26 Dec 2015 13:00:45 +0000")

Ivan Shmakov <ivan@siamics.net> writes:

> 	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”.

If comment about this not being needed was added in 2015 by Stefan.  But
it says that it's "actually" not needed, and "actually not" in common
usage means "absolutely is", so that's quite confusing.

But if it's not needed, then it sounds like we should remove it?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-08-01 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-26 13:00 bug#22243: eieio-opt: not quite (?) optional functions Ivan Shmakov
2019-08-01 17:09 ` Lars Ingebrigtsen [this message]
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=87d0hoke2h.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=22243@debbugs.gnu.org \
    --cc=ivan@siamics.net \
    /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).