From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, 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 10:58:21 -0800 (PST) [thread overview]
Message-ID: <ac20d9d3-c5d8-4c0f-8e3a-be6c05db935b@default> (raw)
In-Reply-To: <<83a6u0n8y7.fsf@gnu.org>>
> 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.
Yep. It's a big doc/help problem, IMO. And
we've moved more and more stuff to things like
`cl-defstruct' (which in itself is fine).
I don't see a good general solution to this
problem. But it is, I think, something
important for the quintessential
"self-documenting" editor. I truly hope that
some smart and ambitious hacker tackles this.
next parent reply other threads:[~2020-12-26 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<E1kt6ez-0000D4-0e@fencepost.gnu.org>
[not found] ` <<83a6u0n8y7.fsf@gnu.org>
2020-12-26 18:58 ` Drew Adams [this message]
2020-12-27 0:51 ` bug#45443: 28.0.50; Can't find definition of compilation--message->loc 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:40 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-27 19:28 ` Unknown
2020-12-26 10:18 Richard Stallman
2020-12-26 10:44 ` Eli Zaretskii
2020-12-27 5:38 ` Richard Stallman
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=ac20d9d3-c5d8-4c0f-8e3a-be6c05db935b@default \
--to=drew.adams@oracle.com \
--cc=45443@debbugs.gnu.org \
--cc=eliz@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).