all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: David Ponce <da_vid@orange.fr>
Cc: 65270-done@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#65270: 30.0.50; `describe-function' issue with some methods
Date: Fri, 15 Sep 2023 05:24:43 -0700	[thread overview]
Message-ID: <CADwFkm=1rjOayDqmyv_4x+dmKU+60wzt91y5ruQKoZ4NCdM-mg@mail.gmail.com> (raw)
In-Reply-To: <93892a01-1c96-4ae8-9a28-67a24a6b2bcf@orange.fr> (David Ponce's message of "Tue, 15 Aug 2023 11:09:00 +0200")

Version: 30.1

David Ponce <da_vid@orange.fr> writes:

> On 15/08/2023 04:40, Stefan Monnier wrote:
>>> It seems there is an issue with `describe-function' of a method that
>>> calls `cl-call-next-method'.  For a such method `describe-function' says
>>> that the method is "Undocumented" even if a doc string is present.
>> I pushed a patch to `master` which seems to fix this problem.
>>
>>> Also the mentioned signature is weird.  See an illustration below using
>>> a simple recipe, running 'emacs -Q'.
>> I think we still have a problem here when the method is not
>> byte-compiled, but I think the problem is in `help-function-arglist`
>> which decides to use the "raw arglist" from the interpreted closure
>> without looking at the arg names stashed in the docstring.
>>          Stefan
>>
>
> Hello Stefan,
>
> I confirm that your patch fixed the issue with doc string, and with
> arglist of byte-compiled methods (which is probably the common case).
>
> Thank you very much!

It seems like this issue was fixed, but it was left open in the bug
tracker.  I'm therefore closing it now.





      reply	other threads:[~2023-09-15 12:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-13 10:36 bug#65270: 30.0.50; `describe-function' issue with some methods David Ponce
2023-08-14 10:41 ` David Ponce
2023-08-14 22:04   ` David Ponce
2023-08-15  2:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-15  9:09   ` David Ponce
2023-09-15 12:24     ` Stefan Kangas [this message]

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='CADwFkm=1rjOayDqmyv_4x+dmKU+60wzt91y5ruQKoZ4NCdM-mg@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=65270-done@debbugs.gnu.org \
    --cc=da_vid@orange.fr \
    --cc=monnier@iro.umontreal.ca \
    /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.