From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61457@debbugs.gnu.org
Subject: bug#61457: 30.0.50; compiler falsely complains missing ‘describe-char-display’
Date: Mon, 13 Feb 2023 09:51:45 +0100 [thread overview]
Message-ID: <d454a013-3d66-f07a-6916-e8ca7b84ac3c@easy-emacs.de> (raw)
In-Reply-To: <83zg9ig064.fsf@gnu.org>
Don't understand why `symbol-function' of `help-fns--analyze-function'
knows about it, but compiler and REPL not.
Am 12.02.23 um 20:21 schrieb Eli Zaretskii:
>> Date: Sun, 12 Feb 2023 19:55:08 +0100
>> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
>>
>> when running ‘M-x byte-compile-file RET’ with the following form in it,
>>
>> ---
>> (describe-char-display (point) (char-after))
>> ---
>>
>> compiler complains:
>>
>> ---
>> In end of data:
>> foo.el:6831:17: Warning: the function ‘describe-char-display’ is not known
>> to be defined.
> Which is correct: you need to (require 'descr-text).
>
>> Whereas ‘M-x describe-function RET’ tells correctly:
>>
>> ---
>> describe-char-display is a byte-compiled Lisp function in
>> ‘descr-text.el’.
>>
>> (describe-char-display POS CHAR)
> Which is also correct.
>
> So what is it that you are complaining about here?
next prev parent reply other threads:[~2023-02-13 8:51 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 [this message]
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
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
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=d454a013-3d66-f07a-6916-e8ca7b84ac3c@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=61457@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).