unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 30223@debbugs.gnu.org
Subject: bug#30223: 27.0.50; Arglist of advised but undefined functions missing
Date: Tue, 17 Apr 2018 22:16:52 +0200	[thread overview]
Message-ID: <87sh7th9l7.fsf@mouse.gnus.org> (raw)
In-Reply-To: <874lndfl9d.fsf@tcd.ie> (Basil L. Contovounesios's message of "Tue, 23 Jan 2018 00:53:50 +0000")

"Basil L. Contovounesios" <contovob@tcd.ie> writes:

> Steps to reproduce:
>
> 1. emacs -Q
> 2. (advice-add 'some-funbound-sym :override #'ignore)
> 3. C-h f some-funbound-sym RET
>
> This results in the *Help* buffer reporting:
>
> some-funbound-sym is .
>
> [Missing arglist.  Please make a bug report.]
>
> Not documented.
>
> [back]
>
> which I presume is at least partially due to
>
>   (get 'some-funbound-sym 'function-documentation)
>     => (advice--make-docstring 'some-funbound-sym)
>
> I wouldn't expect advised-but-undefined functions to have meaningful
> documentation, but IMO the suggestion to make a bug report is
> misleading, given that many users are likely to advise as-of-yet
> undefined functions in their user-init-file.

Yeah, this sounds like something that can happen commonly and there
shouldn't be a "make a bug report" here.

And describe-function should just say that it's a function that's not
defined, but that there's a advice for the symbol, I think?

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





  reply	other threads:[~2018-04-17 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23  0:53 bug#30223: 27.0.50; Arglist of advised but undefined functions missing Basil L. Contovounesios
2018-04-17 20:16 ` Lars Ingebrigtsen [this message]
2021-02-04 11:09 ` 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=87sh7th9l7.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=30223@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /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).