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 15:22:18 +0200 [thread overview]
Message-ID: <87h77bliwl.fsf@gnus.org> (raw)
In-Reply-To: <jwvpmm2atad.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 31 Mar 2022 14:12:41 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Is it worth applying `upcase' to the (nth 1 info) so the result looks
>> more like C-h f output?
>
> If so, we should be careful to only apply it to the argnames but not to
> the specializers since these are case sensitive.
Yup. But, yes, I think it would make sense to upcase/italicize the
argnames, because that would clarify what we're talking about here
(which isn't at all obvious). Patches welcome.
> The above patch also leads to odd results for methods with qualifiers.
> E.g. `C-h o cl-generic-generalizers RET` shows things like:
>
> :extra "cl-struct" (cl-generic-generalizers type) in ‘cl-generic.el’.
>
> Undocumented
>
> which I find rather confusing.
I've now made those things display as before, but I think it's not quite
clear what that part is trying to express, so some clarification here
would be nice.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-02 13:22 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 [this message]
2022-04-02 14:26 ` Stefan Monnier
2022-04-02 14:41 ` Lars Ingebrigtsen
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
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=87h77bliwl.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 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).