From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Robert Pluim <rpluim@gmail.com>, emacs-devel@gnu.org
Subject: Re: master af0ea35ea0: Tweak how functions are formatted in Implementation in *Help*
Date: Sat, 02 Apr 2022 16:41:36 +0200 [thread overview]
Message-ID: <87zgl3im3j.fsf@gnus.org> (raw)
In-Reply-To: <jwvbkxjlgp0.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 02 Apr 2022 10:26:06 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Used internally for the (major-mode MODE) context specializers.
>
> :extra "typeof" (TYPE) in ‘cl-generic.el’.
>
> [...]
>
> The presence/absence of `cl-generic-generalizers` looks rather
> accidental/unexplained (IOW looks like a bug to me :-)
I don't think it's more confusing than before, though. :-/
> For reference, these correspond to:
>
> (cl-defmethod cl-generic-generalizers ((specializer (head derived-mode))))
>
> and
>
> (cl-defmethod cl-generic-generalizers :extra "typeof" (type)
>
> in the source code.
I think the :extra thing should also be formatted as they're supposed to
be used in code. (And I really have no idea what that's supposed to
be.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-02 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164872671963.30191.4037902323881017518@vcs2.savannah.gnu.org>
[not found] ` <20220331113841.3BBFAC0581F@vcs2.savannah.gnu.org>
2022-03-31 13:05 ` master af0ea35ea0: Tweak how functions are formatted in Implementation in *Help* Robert Pluim
2022-03-31 18:12 ` Stefan Monnier
2022-04-02 13:22 ` Lars Ingebrigtsen
2022-04-02 14:26 ` Stefan Monnier
2022-04-02 14:41 ` Lars Ingebrigtsen [this message]
2022-04-02 19:30 ` Stefan Monnier
2022-04-03 11:57 ` Lars Ingebrigtsen
2022-04-03 16:18 ` Stefan Monnier
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=87zgl3im3j.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@gmail.com \
/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.