all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: Eli Zaretskii <eliz@gnu.org>, 61457@debbugs.gnu.org
Subject: bug#61457: 30.0.50; compiler falsely complains missing ‘describe-char-display’
Date: Mon, 13 Feb 2023 14:10:29 -0500	[thread overview]
Message-ID: <jwvsff9758v.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <d454a013-3d66-f07a-6916-e8ca7b84ac3c@easy-emacs.de> ("Andreas Röhler"'s message of "Mon, 13 Feb 2023 09:51:45 +0100")

> Don't understand why `symbol-function' of `help-fns--analyze-function' knows
> about it, but compiler and REPL not.

I believe you're confused:

    ELISP> (symbol-function 'describe-char-display)
    nil
    ELISP> (help-fns--analyze-function 'describe-char-display)
    *** Eval error ***  Symbol’s function definition is void: describe-char-display
    ELISP> 

My crystal ball suggests you have tested these in an Emacs where
`descr-text` happened to be loaded already.


        Stefan






  parent reply	other threads:[~2023-02-13 19:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12 18:55 bug#61457: 30.0.50; compiler falsely complains missing ‘describe-char-display’ Andreas Röhler
2023-02-12 19:21 ` Eli Zaretskii
2023-02-13  8:51   ` Andreas Röhler
2023-02-13 13:59     ` Eli Zaretskii
2023-02-13 19:10     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-13 20:49       ` Eli Zaretskii
2023-02-13 21:01         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-14  3:33           ` Eli Zaretskii
2023-02-14  8:21             ` Andreas Röhler
2023-02-14 13:27               ` Eli Zaretskii
2023-02-15  9:58                 ` Andreas Röhler

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=jwvsff9758v.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=61457@debbugs.gnu.org \
    --cc=andreas.roehler@easy-emacs.de \
    --cc=eliz@gnu.org \
    --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.