From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 45443@debbugs.gnu.org
Subject: bug#45443: 28.0.50; Can't find definition of compilation--message->loc
Date: Sat, 26 Dec 2020 12:44:00 +0200 [thread overview]
Message-ID: <83a6u0n8y7.fsf@gnu.org> (raw)
In-Reply-To: <E1kt6ez-0000D4-0e@fencepost.gnu.org> (message from Richard Stallman on Sat, 26 Dec 2020 05:18:53 -0500)
> From: Richard Stallman <rms@gnu.org>
> Date: Sat, 26 Dec 2020 05:18:53 -0500
>
> Trying to debug a bug in compile-goto-error on Rmail files,
> I typed C-h f compilation--message->loc RET
> then clicked on the file name -- which is supposed to find the definition
> of that function.
>
> It did not find the definition; instead it said,
>
> Unable to find location in file
>
> I also tried M-x find-function RET compilation--message->loc RET.
> It found a call to compilation--message->loc, not the definition.
>
> I searched for that name in the file and did not find a definition.
> I will try grepping for it.
It's a general problem with uses of cl-defstruct and similar
constructs: they generate functions and macros that the Help functions
are unable to find. In this case, see this part of compile.el:
(cl-defstruct (compilation--message
(:constructor nil)
(:copier nil)
;; (:type list) ;Old representation.
(:constructor compilation--make-message (loc type end-loc rule))
(:conc-name compilation--message->))
loc type end-loc rule)
next prev parent reply other threads:[~2020-12-26 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 10:18 bug#45443: 28.0.50; Can't find definition of compilation--message->loc Richard Stallman
2020-12-26 10:44 ` Eli Zaretskii [this message]
2020-12-27 5:38 ` Richard Stallman
[not found] <<E1kt6ez-0000D4-0e@fencepost.gnu.org>
[not found] ` <<83a6u0n8y7.fsf@gnu.org>
2020-12-26 18:58 ` Drew Adams
2020-12-27 0:51 ` Unknown
2020-12-27 8:07 ` Lars Ingebrigtsen
2020-12-27 17:40 ` Eli Zaretskii
2020-12-27 17:59 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-27 18:05 ` Eli Zaretskii
2020-12-27 19:28 ` Unknown
2020-12-27 19:28 ` Unknown
2020-12-27 19:40 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83a6u0n8y7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45443@debbugs.gnu.org \
--cc=rms@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).